My magic ball says you're onCreate adding fragments to activate, and you don't check if there's any other fragment in the activate.I mean, you're gonna have to stick around if there's a fragment and if it's not, add the main fragment.Also, if you have a fragment, don't give me God, it's marked - get it out of there and add it software.

The problem is the misuse of Moxy's library with fragments. Didn't immediately notice the reason. https://github.com/Arello-Mobile/Moxy/issues/50

Why do you have so many static fields? That's why it's coming. EventBus won't help. And in my opinion, eventbus could be called antipatern.

Call these methods. onViewCreated() For example, the fragment hasn't been touched yet.

That's what the activity is. Work with fragments is different. You can add <fragment> In the presentation file or working with fragments through the fragment managers. For example:FragmentTransaction fTrans = getFragmentManager().beginTransaction(); fTrans.add(R.id.frgmCont, frag1); In fact, for a better understanding, read this. http://startandroid.ru/ru/uroki/vse-uroki-spiskom/174-urok-104-android-3-fragments-lifecycle.html and on this website.Through Intent You can't open a fragment. Besides, You can't do "going from activism to fragments."♪ Fragmentation is always associated with activity, it cannot exist separately from activity. So you can open the fragments, replace the fragments, but it's all going to pass through the activity that "the parent" is fragmented/fragments.

You in the listener are downloading a new copy of the dialogue note instead of referring to the discussion. Try to download the method of dialogue and take its note as follows:AlertDialog.Builder builder = new AlertDialog.Builder(getActivity()).setView(R.layout.add_recipe) .setPositiveButton("Додати", new DialogInterface.OnClickListener() { @Override public void onClick(DialogInterface dialog, int which) { AppCompatSpinner spinner; EditText title; EditText description; Dialog view; view = ((Dialog)dialog); ... } }) .setNegativeButton(R.string.cancel, new DialogInterface.OnClickListener() { @Override public void onClick(DialogInterface dialog, int which) { dialog.cancel(); } }); return builder.create();

I found a slice, it's all right. Cossack - in the adapter, folded the terrific text, sealed it, and the black is all because it's black? Bloody negligence)

In method replace The first argument is the ID container for fragments. You're trying to put one fragment in another. This ID should be the same and should indicate the marking element containing your fragments.

Why do you have to be so perverted? savedInstanceStateusing fragments? One of the great reasons for using them is that setRetainInstance(true) in method onCreateView♪This method says that the fragment of the destruction leaves its state and only kills the external image as soon as it is removed from the activism and reenacted, the data are taken from the state of retention.

In MainActivity, I wrote:private static Context cntxt; @Override protected void onCreate(final Bundle savedInstanceState) { super.onCreate(savedInstanceState); setContentView(R.layout.activity_main); cntxt = this; //my logic } In the fragment code:private EditText editText; private boolean flag = false; private View v; @Override public View onCreateView(final LayoutInflater inflater, final ViewGroup container, final Bundle savedInstanceState) { super.onCreate(savedInstanceState); if (!flag) { flag = true; v = inflater.inflate(R.layout.fragment_1, container, false); editText = (EditText) v.findViewById(R.id.editText); } return v; } public MyValues getValues() { final MyValues val = new MyValues(); if (!flag) { flag = true; LayoutInflater inflater = LayoutInflater.from(MainActivity.cntxt); View v = inflater.inflate(R.layout.my_fragment, null, false); edtText = (EditText) v.findViewById(R.id.editText); } val.someTxt = editText.getText() return val; }

When turning, not only activate, but all the fragments are recreated, but if you activate, and you create fragments, it replaces a re-established automobile with an initial condition. You don't need to manually re-create your fragment onCreate activate if the state is being restored, so you need to add a condition:@Override protected void onCreate(Bundle savedInstanceState) { super.onCreate(savedInstanceState); setContentView(R.layout.activity_main); if (savedInstanceState == null) { fragmentTransaction = getSupportFragmentManager().beginTransaction(); fragment = new FragmentList(); fragmentTransaction.replace(R.id.conteiner, fragment); fragmentTransaction.commit(); } } And by the way, in the back of the glass, what do you add? What if he pressed back, he was removed from the actuator and left empty?Also, if you have an activated and fragmented shielding on the screen's orientation, you can just shut off the re-engineering of the activate when you change the orientation by adding an activation in the attribute. android:configChanges="orientation|screenSize|keyboardHidden"

In the manifest for a new Activity, Take it away. Parameter android:parentActivityName=".MainActivity" In Activity, we need to process the click on the Nazad button.@Override public boolean onOptionsItemSelected(MenuItem item) { int id = item.getItemId(); if (id == android.R.id.home) { finish(); } }

Every time a new instance activity was created on the UP button without parameters, which triggered NPE to open the activity in the state that it was, in the manifest, it needs to describe the atribut. android:launchMode="singleTop"

Use ViewPager for swaps between fragments. You'll be glad to see him in the adapter! I'll bring the code for the basic solution below.Create a laiate from the viewpager:<?xml version="1.0" encoding="utf-8"?> <LinearLayout xmlns:android="http://schemas.android.com/apk/res/android" android:layout_width="match_parent" android:layout_height="match_parent" android:orientation="vertical"> &lt;android.support.v4.view.ViewPager android:id="@+id/vpPager" android:layout_width="match_parent" android:layout_height="wrap_content"&gt; &lt;/android.support.v4.view.ViewPager&gt; </LinearLayout> Then we create a few fragments that will be in our viewpager. The next step will be to create an adapter and assign it to our viewpager:public static class MyPagerAdapter extends FragmentPagerAdapter { private static int NUM_ITEMS = 3; public MyPagerAdapter(FragmentManager fragmentManager) { super(fragmentManager); } // Возвращает общее количество фрагментов @Override public int getCount() { return NUM_ITEMS; } // Возвращает фрамгент, который будет отображаться сейчас @Override public Fragment getItem(int position) { switch (position) { case 0: // Fragment # 0 - This will show FirstFragment return FirstFragment.newInstance(0, "Page # 1"); case 1: // Fragment # 0 - This will show FirstFragment different title return FirstFragment.newInstance(1, "Page # 2"); case 2: // Fragment # 1 - This will show SecondFragment return SecondFragment.newInstance(2, "Page # 3"); default: return null; } } // Возвращает заголовок (например, если используете TabLayout) @Override public CharSequence getPageTitle(int position) { return "Page " + position; } } And after that, our adapter is assigned to our viewpager in the activate code:... ViewPager vpPager = (ViewPager) findViewById(R.id.vpPager); adapterViewPager = new MyPagerAdapter(getSupportFragmentManager()); vpPager.setAdapter(adapterViewPager); ...

It's not clear from the description what the problem is. ♪ ♪ But you can try this:recyclerView.addItemDecoration(new DividerItemDecoration(getContext(), LinearLayoutManager.VERTICAL));

Fragment in the fragment is not a good idea. Try to avoid it.Yes, it is. But only if the data are true. You don't have to redesign the adapter just to work for all possible cases. Better make some.Just put another one in the cell. But it's better not to do that, it might be a problem. On the other hand, ViewPager/ScrollView inside the RecyclerView cells is working well.It's best to open a separate activism. It's so much more control and logic.

After a long time ago, I never figured out how to change the view. The problem was solved by a crutch. Started the method notifyDataSetChanged() 300 milliseconds, and it's working.mHandler = new WeakHandler(); mHandler.postDelayed(new Runnable() { @Override public void run() { mPagerAdapter.notifyDataSetChanged(); mPagerFoto.setCurrentItem(positionFoto); } }, 300);

I've killed a lot of nerves on fragments and decided to do dynamically. Change your code in the activate mark.<fragment android:layout_width="match_parent" android:layout_height="wrap_content" android:name="com.vkramarenko.myapplication.TextFragment" android:id="@+id/textFragment" android:layout_above="@+id/No" android:layout_alignEnd="@+id/No" /> Freimelaut.<FrameLayout xmlns:android="http://schemas.android.com/apk/res/android" xmlns:app="http://schemas.android.com/apk/res-auto" xmlns:tools="http://schemas.android.com/tools" android:id="@+id/frgmCont" <!--по этому id будем обращаться--> android:layout_width="match_parent" android:layout_height="match_parent" tools:context=".ТвоеАктивити" > Example of fragmentation: frame.xml at my window.<FrameLayout xmlns:android="http://schemas.android.com/apk/res/android" xmlns:tools="http://schemas.android.com/tools" android:layout_width="match_parent" android:layout_height="match_parent" tools:context="com.бла-бла.бла.КлассФрейма"> <TextView android:layout_width="match_parent" android:layout_height="match_parent" android:text="@string/hello_blank_fragment" /> Freima class creates a master and there's the most important thing.public View onCreateView(LayoutInflater inflater, ViewGroup container, Bundle savedInstanceState) { // R.layout.frame - имя твоего xml для фрейма View rootView = inflater.inflate(R.layout.frame, container, false); return rootView; } And then to show off the frime at the moment you need to decorate it (on onclick or activate:getFragmentManager().beginTransaction().addToBackStack(null).replace(R.id.frgmCont,new КонструкторФрагмента() ).commit(); new Designator Fragmentation(s) may be replaced by Fragment.newInstance (the Master creates this method)If you use the Compatibility Library, getSupportedFragmentManager()

You're not syntaxically casting the result of a class challenge. You need to do that by surrounding the brackets:((MainActivity)getActivity()).METHOD_FROM_MAIN_ACTIVITY_CLASS(); Or so, by creating the necessary variable:MainActivity activityMain = (MainActivity) getActivity(); activityMain.METHOD_FROM_MAIN_ACTIVITY_CLASS();

Use SharedPreferencesRecord:String name = ...; SharedPreferences pref = PreferenceManager.getDefaultSharedPreferences(context); pref.edit().putString("name", name).apply(); We read:SharedPreferences pref = PreferenceManager.getDefaultSharedPreferences(context); String name = pref.getString("name", ""); So, at the time of the recording, you'll keep your data, and when you show the fragment, you can get them and take them off.