I ran into an issue where something in the latest version of the Command Lines Tools/Required Resources package for B4A 13 caused my app to break, when it worked with B4A 11.5 and it's version of the tools package.
Luckily, when I replaced the tools with the ones from v11, the app worked with B4A v13 even when setting the TargetSDK to 34 (I think I used the SDK manager to download the SDK Platform 34 install module.
Yeah, I could spend a bunch of time rewriting my code to use a different drawer than NSNavigationDrawer (which was causing the problem), but why should I need to do that if simply using an older version of the Tools allows it to work?
I am hoping that it would be easy to update a post that has links to the different versions of the SDK tools.
Also, from what I can tell, it looks like the IDE will use the SDK/tool package that is pointed to by the "android.jar" path setting in the IDE. So, maybe a new compiler directive could be added so that I can override that setting and specify a different SDK tools directory for a particular project. This way I can install and use the latest tool package for most of my apps (as you recommend), but can use an older package instead of having to spend a bunch of time to fix something that really doesn't need to be fixed if it works by simply using an older version of the tools.
Luckily, when I replaced the tools with the ones from v11, the app worked with B4A v13 even when setting the TargetSDK to 34 (I think I used the SDK manager to download the SDK Platform 34 install module.
Yeah, I could spend a bunch of time rewriting my code to use a different drawer than NSNavigationDrawer (which was causing the problem), but why should I need to do that if simply using an older version of the Tools allows it to work?
I am hoping that it would be easy to update a post that has links to the different versions of the SDK tools.
Also, from what I can tell, it looks like the IDE will use the SDK/tool package that is pointed to by the "android.jar" path setting in the IDE. So, maybe a new compiler directive could be added so that I can override that setting and specify a different SDK tools directory for a particular project. This way I can install and use the latest tool package for most of my apps (as you recommend), but can use an older package instead of having to spend a bunch of time to fix something that really doesn't need to be fixed if it works by simply using an older version of the tools.
