help...
just updated the SDK through SDK Manager
all went ok
now when trying to run a project in debug mode I get the following
Maven artifact not found: androidx.annotation/annotation-experimental
what should i do ?
my B4A version is 10.50
SDK manager version is 3.71
it's kind of urgent as it is in the middle of work...
maybe it has something to do with access permissions ?
i used to access external memory
now i try internal
that doesn't seem to need any permission
i try to use - SaveDir = File.DirInternal
that seems to be failing when i try to access the file
is this make any sense ?
SHAME, SHAME ON ME !!!
i apologize for wasting your time and patience
it was my fault
i was sure i removed all references to phone functions and thanks to you had found one
now all is working
thank you so much for your patience and support
I have to assume that for some reason you need this component but I do wonder why? Assuming you have correctly installed the SDK as we previously told you, open SDK Manager, Deselect All, search for 'experimental', select ONLY androidx.annotation.annotation-experimental and Install Selected.
thanks
i don't know why i need it - i first saw it today after the sdk update
did what you say and now i get this error (on both debug & release)
B4A Version: 10.50
Parsing code. (0.14s)
Java Version: 8
Building folders structure. (0.57s)
Compiling code. (0.22s)
Compiling layouts code. (0.03s)
Organizing libraries. (0.00s)
(AndroidX SDK)
Generating R file. Error
c:\android\tools\..\extras\b4a_remote\androidx\savedstate\savedstate\1.1.0\unpacked-savedstate-1.1.0\res\values\values.xml:3: error: Found tag id where item is expected
c:\android\tools\..\extras\b4a_remote\androidx\lifecycle\lifecycle-viewmodel\2.3.0\unpacked-lifecycle-viewmodel-2.3.0\res\values\values.xml:3: error: Found tag id where item is expected
c:\android\tools\..\extras\b4a_remote\androidx\lifecycle\lifecycle-runtime\2.3.0\unpacked-lifecycle-runtime-2.3.0\res\values\values.xml:3: error: Found tag id where item is expected
yes!!
now it is all perfect
once again thank you very much
why do i need that experimental object ?
why use experimental objects at all ?
i never needed it, on 28 it is not required just the change to 29 dropped it on me...
c:\android_sdk\tools\..\extras\b4a_remote\androidx\savedstate\savedstate\1.1.0\unpacked-savedstate-1.1.0\res\values\values.xml:3: error: Found tag id where item is expected
c:\android_sdk\tools\..\extras\b4a_remote\androidx\lifecycle\lifecycle-viewmodel\2.3.0\unpacked-lifecycle-viewmodel-2.3.0\res\values\values.xml:3: error: Found tag id where item is expected
c:\android_sdk\tools\..\extras\b4a_remote\androidx\lifecycle\lifecycle-runtime\2.3.0\unpacked-lifecycle-runtime-2.3.0\res\values\values.xml:3: error: Found tag id where item is expected
el.
Oops
Anything i need to do other than change the target in the manifest?
I changed it to 30 but the app crashes now
If i return to 28 it works perfectly
Any idea?
Thanks
Just updated the SDK through the B4A SDK Manger and now I get the "Maven artifact not found: com.google.guava/listenablefuture". I tried searching for it, and this is closest one installed: I see that others had this issue in the past - seems that updates to the SDK Manager to 3.6 fixed it...
Just updated the SDK through the B4A SDK Manger and now I get the "Maven artifact not found: com.google.guava/listenablefuture". I tried searching for it, and this is closest one installed: I see that others had this issue in the past - seems that updates to the SDK Manager to 3.6 fixed it...
had exactly the same problem
needed to update the SDK
than i got many other problems
look at this topic from the beginning
my problems are gone now thanks to help from the good people here
yes!!
now it is all perfect
once again thank you very much
why do i need that experimental object ?
why use experimental objects at all ?
i never needed it, on 28 it is not required just the change to 29 dropped it on me...
That and the Android SDK Command line tools (same place) comprise the whole Android environment b4a needs.
There are a exceptions, but when you need them, you'll know enough to know how and why.