The FragmentManager class is responsible to make interaction between fragment objects. Fragments represent multiple screen inside one activity.Īndroid fragment lifecycle is affected by activity lifecycle because fragments are included in activity.Įach fragment has its own life cycle methods that is affected by activity life cycle because fragments are embedded in activity. There can be more than one fragment in an activity. Thank you.Android Fragment is the part of activity, it is also known as sub-activity. Cleaning my projects fixed this issue for me. Thanks for starting this thread and identifying possible solutions. I've tried the following "fixes" previously mentioned in various places on the forum, but none seem to work:Īre there others having any issues? If not, does anyone else know how to resolve it? I've tried debugging on an actual device and on emulators (Genymotion) running both Android 4.4.4 and 5.1.0, but no matter what, no breakpoints are hit.
I am running the latest version of Xamarin for VS, we are using Xamarin Forms, and we have a PCL as our shared library.
The most recent issues seem to state that this is only affecting iOS and is fixed on Android, but I am having the issue with Android, and it seems to be more prominent/happen all the time after I performed the latest Xamarin upgrade. I've seen a lot of issues with breakpoints not being hit for Xamarin. Also, you need to edit the SLN file because it contains a reference to the path of each project in the solution - so make the change there too. If you try this, bear in mind it is the physical folder name not the project name that is important. It turns out that the MDB files are the way that debugging information gets packaged up into the APK - without it you can't debug! I think they are created by a tool called PDB2MDB.exe during the build process. The thing that nailed it for me was noticing that when I did a clean build, the bin/debug folder did not contain an "MDB" file for the main exe (in this case Engagement ) and so was not been packaged into APK file. Other symptoms that went with this included the "Clean Project" option not clearing all the files from the bin/debug folder (it left behind the project's main DLL and PDB file). When I changed the folder name to "Engagement_Android" (keeping the same project name) - it started hitting breakpoints again. Brand new projects that I added (called Test1, Test2, etc) - debugged perfectly.
No matter what I did, it wouldn't hit breakpoints. \Engagement (Android)\Engagement (Android).csproj I had a Xamarin Android project called "Engagement (Android)" within a solution, and by default it was stored on disk at. The folder name is often the same as the project name, but it doesn't have to be. Do you have any spaces or punctuation characters in yours? I've found that the name of the folder that contains your project can make a difference.
0 kommentar(er)
