Android Question Error after updating maven files with the sdk manager

G

Grant Fullen

Member

Licensed User

• Dec 14, 2017

• #2

EDIT: Now a brand new unmodified project gives this on compile.

Failure [-26: Package b4a.example new target SDK 19 doesn't support runtime permissions but the old target SDK 23 does.]

I am using the new 7.80 Beta #1

 

Upvote 0

G

Grant Fullen

Member

Licensed User

• Dec 14, 2017

• #3

If I increase the Minimum SDK version it gets rid of that message and compiles. However, simply enabling the RuntimePermissions library now triggers a bunch of errors.

 

Upvote 0

G

Grant Fullen

Member

Licensed User

• Dec 14, 2017

• #4

It looks like the SlidingMenu from here https://www.b4x.com/android/forum/threads/jfeinstein10-slidingmenu-library.36482/#content is broken now too. Just by simply including this library it throws errors.

 

Upvote 0

G

Grant Fullen

Member

Licensed User

• Dec 14, 2017

• #5

If this is something I just need to downgrade until solutions are found, then please can someone help me figure that out. I upgraded all of the recommended Maven libs using the built in SDK Manager and now I'm stuck and broken.

 

Upvote 0

G

Grant Fullen

Member

Licensed User

• Dec 14, 2017

• #6

So I have uninstalled absolutely everything from B4A to deleting the android-sdk folder. I re-installed and re-downloaded everything and I'm still having these basic issues. Surely someone else is broken now too because these are vanilla projects I'm trying to get compiled.

 

Upvote 0

G

Grant Fullen

Member

Licensed User

• Dec 14, 2017

• #7

So after messing around a lot I kept the same original values in the manifest editor: minSdkVersion="5" android:targetSdkVersion="19"

Under Tools -> Configure Paths I changed the android jar to the android-27\android.jar. It was 24. Now things seem back to normal...... so far.

 

Upvote 0