-
Notifications
You must be signed in to change notification settings - Fork 715
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
BREAKING CHANGES coming up #922
Comments
This was referenced Mar 12, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
updated:
armeabi
target (superseded byarmeabi-v7a
, seems to be not supported by Android 5.0) to be dropped as I had proposed in Ending support for old Android versions #771, for the following reasons:armeabi
target CPUcode
will always be0
(Error code member going away #821; was part of Major release with possible enhancements & breaking changes #773)location
numeric values of0
,1
, and2
will be rejected; must uselocation: 'default'
oriosDatabaseLocation
setting as documented (was part of Major release with possible enhancements & breaking changes #773)androidDatabaseImplementation: 2
setting which is now superseded byandroidDatabaseProvider: 'system'
settingkey
orcreateFromLocation
is usedunder consideration:
androidLockWorkaround
option if it is not needed by the user community any longerother:
The text was updated successfully, but these errors were encountered: