You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It looks like the 1.3.0 update introduced errors related to missing hasVerticalAccuracy symbols. I am seeing the following error when trying to run the NDK example, after the 1.3.0 update:
NOTE: I was able to successfully run the same example with version 1.2.1.
NOTE-2: I was able to reproduce the error on a Samsung Galaxy S8 with Android 7 (API level 25), and a One Plus 5 with Android 7 (API level 25). It looks like android.location.Location::hasVerticalAccuracy() was added in API level 26.
NOTE-3: I finally got the NDK demo working by upgrading my Samsung S8 to Android 8 (API level 26), and setting the minSdkLevel to 26 on app/build.gradle. Not supporting API level < 25 is still a problem though.
Really sorry, you are 100% right. The 1.3.0 release has a regression on this area, where we bumped, without noticing, our minimum API level support to 26. We are fixing this in our next release, which is coming out soon.
It looks like the
1.3.0
update introduced errors related to missinghasVerticalAccuracy
symbols. I am seeing the following error when trying to run the NDK example, after the1.3.0
update:NOTE: I was able to successfully run the same example with version
1.2.1
.NOTE-2: I was able to reproduce the error on a Samsung Galaxy S8 with Android 7 (API level 25), and a One Plus 5 with Android 7 (API level 25). It looks like
android.location.Location::hasVerticalAccuracy()
was added in API level 26.NOTE-3: I finally got the NDK demo working by upgrading my Samsung S8 to Android 8 (API level 26), and setting the
minSdkLevel
to 26 onapp/build.gradle
. Not supporting API level < 25 is still a problem though.The text was updated successfully, but these errors were encountered: