-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Android crash when displaying map on Samsung Galaxy Tab (SM-T230NU) #3247
Comments
This 's happened on my Nexus 7, the error seem to like yours. Are you use the custom image for sprite marker? If so I think you should try to reduce the size of that image. After I did that, it doesn't crash anymore. |
@vfaSonnt, we are using custom markers but they're only 24dp[0]. |
@niedzielski Are you still experiencing this issue? |
@bleege, we have a regression test slated for tomorrow. I'll follow up here when I hear back. |
@niedzielski Sounds good. Please let us know what version of the SDK is in use. If there is any issue you should feel free to swap in |
@bleege, we're on v2.3 currently and were planning to upgrade to the next release as soon as it came out[0]. If we're still seeing the crash, I'll try to get 4.0.0-SNAPSHOT tested. |
@bleege, it sounds like QA still repros this issue (on v2.3) :( I'd like to try the 4.0.0-SNAPSHOT but it looks like there's a lot of API changes. In the past, we've just kind of "felt around" for Mapbox SDK version differences and tried to test well. Are there official release notes we should be reading? I can never find them but I always see the awesome ones for iOS under releases so I wondered if they're just stored some place I'm completely missing. The Mapbox tree moves pretty fast so any docs you can point to help guide the upgrade would be much appreciated. |
@niedzielski, this changelog has a rundown of the changes between each Android and iOS SDK release. The Android SDK 4.0.0 release notes will be added in time for the release, if not sooner. |
👍 @1ec5, this is great! Is there anything that would also describe the API differences like renaming Sprite to Icon? |
I noticed that this device is included within AWS device farm, Currently running tests against it. |
|
Is your device the same as in this screenshot? |
@niedzielski thank you for confirming. This means that we were able to run the |
QA confirms this is fixed in 4.0.0. Thanks! |
Awesome! Thanks for confirming @niedzielski! |
Hello! One of users was able to produce a native crash and sent in the appended logcat. This is likely on version SDK v2.2.0 but possibly v2.3.0. We're working to obtain more information. Is a symbol archive available for each release? I've built the SDK but would be more confident using symbols recorded in the original release.
If I have the lib version and architecture right, here's the dump I get:
The text was updated successfully, but these errors were encountered: