-
Notifications
You must be signed in to change notification settings - Fork 109
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
my app freeze on iOS 13 due to the routes #376
Comments
I've also seen this, but am not yet sure what the solution is. I don't know if it's in MapKit or TK. I will continue to monitor |
Could you please try build 2.1.96 and get back to me? <PackageReference Include="TK.CustomMap" Version="2.1.96" /> |
Hello thanks a lot for your feedback, unfortunatly I still have the issue :( |
oh balls. |
well @LeeMaZong I did yet another round of disposal work <PackageReference Include="TK.CustomMap" Version="2.1.97" /> |
nevermind, I'm still seeing it under certain scenarios |
i'm facing exact issue on version 2.1.97 in iOS 13 & above . Any updated please let me know |
@ChaseFlorell Hope everything works well! We are having some users complaining about this freeze too when they go back and forth around the field details/edit page. Any update on this? |
@Alex-Wang08 no update yet, feel free to fork and PR a fix, I'm happy to merge your pr. |
Hello and thanks for your work on TKCustomMap.
I use a TKCustomMap with routes, all is ok on Android and iOS until 12.4 but not on iOS 13 (only the 13 and more) there is a problem.
The problem is when I go in a page with the map and routes, I can open this page go back, open again this page between 5 and 10 times but after that my app freezes.
I give you the error stack of my application output at the end.
I found this on the web witch looks like our issue:
https://forums.xamarin.com/discussion/171095/xamarin-ios-application-freezes-on-ios-13
when I don't show any routes all the application is OK in iOS 13.
=================================================================
Native Crash Reporting
Got a SIGSEGV while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=================================================================
Native stacktrace:
=================================================================
Basic Fault Address Reporting
Memory around native instruction pointer (0x7fff48cab625):0x7fff48cab615 48 8b 7f 08 48 85 ff 74 13 48 8b 73 10 48 8b 07 H...H..t.H.s.H..
0x7fff48cab625 ff 50 10 b8 ad ba ad de 48 89 43 10 48 83 c4 08 .P......H.C.H...
0x7fff48cab635 5b 5d c3 55 48 89 e5 53 50 48 89 fb 48 8d 05 78 [].UH..SPH..H..x
0x7fff48cab645 37 eb 3d 48 89 07 48 8b 7f 08 48 85 ff 74 0a 48 7.=H..H...H..t.H
=================================================================
Managed Stacktrace:
=================================================================
The text was updated successfully, but these errors were encountered: