Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
Created attachment 9370 [details]
When in a MapPage, which is in a NavigationPage that is a child of a TabbedPage, tapping on an annotation causes the app to freeze or crash. The same does not occur if this is done outside of a TabbedPage. There are no handlers for tapping the annotation. And error in the console when the annotator is tapped is:
>Missing method Android.Gms.Maps.GoogleMap.InfoWindowClickEventArgs::get_P0() in assembly /storage/emulated/0/Android/data/com.onobytes.mapannotationfreeze/files/.__override__/GooglePlayServicesLib.dll, referenced in assembly /storage/emulated/0/Android/data/com.onobytes.mapannotationfreeze/files/.__override__/Xamarin.Forms.Maps.Android.dll
It is worth noting that trying to do a release build with the default linker options, Link SDK Assemblies Only, causes the build to fail with a similar error that refers to the same method. Building in Debug works as expected though. The error when building in Release as above is:
>/Library/Frameworks/Mono.framework/External/xbuild/Xamarin/Android/Xamarin.Android.Common.targets: Error: Error executing task LinkAssemblies: error XA2006: Reference to metadata item 'Android.Gms.Maps.Model.Marker Android.Gms.Maps.GoogleMap/InfoWindowClickEventArgs::get_P0()' (defined in 'Xamarin.Forms.Maps.Android, Version=18.104.22.168, Culture=neutral, PublicKeyToken=null') from 'Xamarin.Forms.Maps.Android, Version=22.214.171.124, Culture=neutral, PublicKeyToken=null' could not be resolved. (MapAnnotationFreeze.Droid)
Note that the method in both of those errors is:
I am not going to file a separate bug for the Release build issue as at this point they issues seem related. Note also that doing a release build with Linker set to "None" builds and launches but sill crashes when the annotation is tapped, and a similar error message is seen in the logcat, so this does not seem to be a linker bug?
## Steps to reproduce
1. Open test project, restore packages, and launch a Debug build of the Android app project.
2. Click the Go To Map button
3. Tapp in the pin.
4. Tap on the annotation.
5. Tap the back button (either in the action bar or the main back button)
Expected Result: App will return to the previous page
Actual Result: App does not return to the previous page but remains locked on the MapPage.
## Additional note
If you launch the debug build of the app when disconnected from the debugger, the app will crash when the annotation is tapped. Then looking in the logcat I see the same missing method exception:
>I/MonoDroid(18640): UNHANDLED EXCEPTION:
>I/MonoDroid(18640): System.MissingMethodException: Method not found: 'Android.Gms.Maps.GoogleMap.InfoWindowClickEventArgs.get_P0'.
>I/MonoDroid(18640): at Android.Gms.Maps.GoogleMap/IOnInfoWindowClickListenerImplementor.OnInfoWindowClick (Android.Gms.Maps.Model.Marker) <0x00073>
>I/MonoDroid(18640): at Android.Gms.Maps.GoogleMap/IOnInfoWindowClickListenerInvoker.n_OnInfoWindowClick_Lcom_google_android_gms_maps_model_Marker_ (intptr,intptr,intptr) <0x0005f>
>I/MonoDroid(18640): at (wrapper dynamic-method) object.d22f49bc-db4d-4194-8d20-e4e2ccc32c91 (intptr,intptr,intptr) <0x00043>
I have checked this issue and I am able to reproduce this issue.
Observations: When I deploy the attach project and follow the steps mentioned in the bug description I observed that after clicking back button application does not return to previous page and shows not responding message, i.e. "MapAnnotationFreeze isn’t responding."
Application Output: https://gist.github.com/RamChBachkheti/9d4c6ada856180979cca
IDE logs: https://gist.github.com/RamChBachkheti/22556d87885b228a1da1
Device logs: https://gist.github.com/RamChBachkheti/3a17db8ddad3f0f84acc
Please let me know if I can provide more info to this issue.
=== Xamarin Studio ===
Version 5.7 (build 661)
Installation UUID: 6ea47b0d-1852-4aaf-808d-373ff0a5002b
Mono 3.12.0 ((detached/a813491)
GTK+ 2.24.23 (Raleigh theme)
Package version: 312000068
=== Apple Developer Tools ===
Xcode 6.1 (6604)
=== Xamarin.iOS ===
Version: 126.96.36.199 (Trial Edition)
Build date: 2015-01-08 13:39:32-0500
=== Xamarin.Android ===
Version: 188.8.131.52 (Trial Edition)
Android SDK: /Users/jatin66/Desktop/Backup/android-sdk-macosx
Supported Android versions:
1.6 (API level 4)
2.1 (API level 7)
2.2 (API level 8)
2.3 (API level 10)
3.1 (API level 12)
4.0 (API level 14)
4.0.3 (API level 15)
4.1 (API level 16)
4.2 (API level 17)
4.3 (API level 18)
4.4 (API level 19)
4.4.87 (API level 20)
5.0 (API level 21)
Java SDK: /usr
java version "1.7.0_65"
Java(TM) SE Runtime Environment (build 1.7.0_65-b17)
Java HotSpot(TM) 64-Bit Server VM (build 24.65-b04, mixed mode)
=== Xamarin.Mac ===
Version: 184.108.40.206 (Trial Edition)
=== Build Information ===
Release ID: 507000661
Git revision: b70bab61da996da29045ea8ee8aed1a6faedbe78
Build date: 2015-01-05 16:31:31-05
Xamarin addins: 82f6c71490562d6cd125a09287f441902fdac3d7
=== Operating System ===
Mac OS X 10.10.0
Darwin Jatin66s-iMac.local 14.0.0 Darwin Kernel Version 14.0.0
Fri Sep 19 00:26:44 PDT 2014
Just for reference, it looks like the exception message about the missing method is hitting a debugger bug 25356. The "freezing" behavior is happening because the debugger has caught the missing method exception and paused the application.
This app uses Google Play Service 22. I was able to reproduce the original symptoms on XF 1.3.1. I then double-checked the behavior of the test app with the latest Forms pre-release:
Google Play Services 220.127.116.11
The app no longer hits the exception, and tapping the back button successfully navigates back to the original page. This is a duplicate of 25779.
*** This bug has been marked as a duplicate of bug 25779 ***