Release Android v6.1.3

[LukasPaczos]

Today we are releasing the 6.1.3 version of Mapbox Maps SDK for Android.

Feedback

Please report any issues you have with this release here. For support questions please use StackOverflow or reach out to us through support.

Changes since v6.1.2

• Circle querying fixes #11571
• Global symbol query #11742
• Change MapView#initialize modifier to allow overriding #11969
• Update telemetry to 3.1.2 #11987

Todo

• Create release branch
• Change CircleCI config to build from release branch (android-release-all->deploy)
• Change version name to 6.1.3 in /platform/android/MapboxGLAndroidSDK/gradle.properties
• Publish 6.1.3 artifact to Maven Central
• Tag android-v6.1.3
• Change version name to 6.1.4-SNAPSHOT in /platform/android/MapboxGLAndroidSDK/gradle.properties
• Change CircleCI config to build back from release branch
• Merge release-android-v6.1.3 back into release-boba
• If stable version, Make new cnplgn release @cammace
• Update the android-docs repo's javadoc documentation via release tag's .zip folder @langsmith
• Update SDK version in android-docs repo's constants.js file @langsmith
• Update Mapbox demo and wearable demo apps @langsmith
• If stable version, update mapbox-plugins-android test app @langsmith
• update the style specification’s SDK support tables @langsmith note~~
• Update version # in config files in /help @langsmith
• Update version # in src > constants.js file in /www.mapbox.com @langsmith
• Update version # in pthfndr @langsmith
• Update version # in Studio Preview @langsmith
• Update version # in master&navUI branches of Store Locator kit @langsmith
• Create new tag/release in demo app repo @langsmith
• Release new version of Android demo app on Play Store @langsmith
• If stable version, update # in cnplgn @langsmith
• If stable version, update # in vyge @langsmith

---

/cc @mapbox/mobile @mapbox/support @colleenmcginnis

[ben-j69]

The SDK v6 does not work because of telemtry issue

java.lang.ClassCastException: android.os.BinderProxy cannot be cast to com.mapbox.android.telemetry.TelemetryService$TelemetryBinder at com.mapbox.android.telemetry.MapboxTelemetry$3.onServiceConnected(MapboxTelemetry.java:374)

[langsmith]

@tobrun @LukasPaczos , this is done on my end...

[stoefln]

@ben-j69 same here

[zugaldia]

@ben-j69 @stoefln Are you referring to mapbox/mapbox-events-android#157 or are you referring to a separate issue? If so, sorry to hear you're hitting this problem, we're actively working on it and we're planning to include a fix in the next release as soon as that PR lands.

[stoefln]

I am referring to

java.lang.ClassCastException: android.os.BinderProxy cannot be cast to com.mapbox.android.telemetry.TelemetryService

[zugaldia]

@ben-j69 @stoefln Please see #11994 (comment) - this crash should be fixed now. If not, please do let us know. Thanks!

[BharathMG]

@zugaldia We are seeing android.os.BinderProxy cannot be cast to com.mapbox.android.telemetry.TelemetryService$TelemetryBinder sometimes in 6.2.1 when app starts or stops.

[zugaldia]

@zugaldia We are seeing android.os.BinderProxy cannot be cast to com.mapbox.android.telemetry.TelemetryService$TelemetryBinder sometimes in 6.2.1 when app starts or stops.

@electrostat Is mapbox/mapbox-events-android#174 the best place to track this issue, or should we cut a new one?

[electrostat]

@zugaldia yep that's the best place to track it. On my list to get to and start investigating/solving.

@BharathMG could you provide some example code for me to test my solution against?

[rhuttenh]

I am on version 6.2.1 of the sdk and version 0.2.0 of core with the current plugins. I am still getting this error in my service that issues location updates to the UI. I was able to fix the issue for now by including

<meta-data android:name="com.mapbox.EnableEvents" android:value="false" />

in my manifest.
Do you have a fix for this yet?

[electrostat]

@rhuttenh @BharathMG check the latest snapshot of core: 0.3.0-SNAPSHOT. It should have the fix you need. If you are still running into issues, please reach out in our events repo: https://github.com/mapbox/mapbox-events-android

[rhuttenh]

Nope that did not work. Still the same error. I turned it back on in my manifest so that I can continue work. What are my next steps to help you fix the error. I am new to filing issues on GitHub. Sorry

…

On Jul 16, 2018, at 10:22 AM, Anthony Agby ***@***.***> wrote: @rhuttenh <https://github.com/rhuttenh> @BharathMG <https://github.com/BharathMG> check the latest snapshot of core: 0.3.0-SNAPSHOT. It should have the fix you need. If you are still running into issues, please reach out in our events repo: https://github.com/mapbox/mapbox-events-android <https://github.com/mapbox/mapbox-events-android> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#11990 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEHeiSQEGAyxjL9tcUkizp0i3I5HjOnmks5uHK-pgaJpZM4UKLjZ>.

[electrostat]

@rhuttenh use this link: https://github.com/mapbox/mapbox-events-android/issues/new and provide all the details of the bug you are experiencing. Crash logs would be helpful. Additionally, please provide a code example so I can replicate the bug. Any other details that you think would be helpful would be appreciated (OS version, devices crash is occurring on, sdk versions, etc...)