Gianni Sassanelli Active Member Licensed User Longtime User Aug 28, 2024 #1 Hi, as from subject, if i Try to run b4a sdk manager it waiting for infinite time. can i have help please? thanks Attachments 1724829956961.png 36.9 KB · Views: 389
Hi, as from subject, if i Try to run b4a sdk manager it waiting for infinite time. can i have help please? thanks
DonManfred Expert Licensed User Longtime User Aug 28, 2024 #3 Gianni Sassanelli said: can i have help please? Click to expand... What are the paths you set in the IDE? Tools-Configure Paths Upvote 0
Gianni Sassanelli said: can i have help please? Click to expand... What are the paths you set in the IDE? Tools-Configure Paths
Gianni Sassanelli Active Member Licensed User Longtime User Aug 28, 2024 #4 Sagenut said: Which B4A version? Click to expand... 12.80 Upvote 0
Gianni Sassanelli Active Member Licensed User Longtime User Aug 28, 2024 #5 DonManfred said: What are the paths you set in the IDE? Tools-Configure Paths Click to expand... Upvote 0
DonManfred Expert Licensed User Longtime User Aug 28, 2024 #6 Based on the instructions it should look like Unzip in the same folder. It should look like this: and the path to sdkmanager.bat should be C:\Android30\cmdline-tools\bin\sdkmanager.bat Additional you should have C:\Android30\platforms\android-34\android.jar set... Looks like your installtion is not really ok.... Upvote 0
Based on the instructions it should look like Unzip in the same folder. It should look like this: and the path to sdkmanager.bat should be C:\Android30\cmdline-tools\bin\sdkmanager.bat Additional you should have C:\Android30\platforms\android-34\android.jar set... Looks like your installtion is not really ok....
Erel B4X founder Staff member Licensed User Longtime User Aug 28, 2024 #7 Follow the updated instructions: https://www.b4x.com/b4a.html Upvote 0
Sagenut Expert Licensed User Longtime User Aug 28, 2024 #8 Gianni Sassanelli said: View attachment 156434 Click to expand... You should point to Android-33.jar (for B4A 12.80 but now B4A 13 is available). And you should put the Java folder outside from Program Files, make something like C:\Java Program Files it's a system restricted folder and can cause access problems. Upvote 0
Gianni Sassanelli said: View attachment 156434 Click to expand... You should point to Android-33.jar (for B4A 12.80 but now B4A 13 is available). And you should put the Java folder outside from Program Files, make something like C:\Java Program Files it's a system restricted folder and can cause access problems.
Gianni Sassanelli Active Member Licensed User Longtime User Aug 28, 2024 #9 thanks Sagenut, Erel, DonManfred. i have corrected my paths as your suggestion. now i have the following configuration but SDK manager not work With B4a 13.0 Android sdk34 JAVA 19.0.2 the problem remain Upvote 0
thanks Sagenut, Erel, DonManfred. i have corrected my paths as your suggestion. now i have the following configuration but SDK manager not work With B4a 13.0 Android sdk34 JAVA 19.0.2 the problem remain
asales Expert Licensed User Longtime User Aug 28, 2024 #10 Gianni Sassanelli said: thanks Sagenut, Erel, DonManfred. i have corrected my paths as your suggestion. now i have the following configuration but SDK manager not work Click to expand... Do you are using the recommended SDK by Erel or only change the paths? Upvote 0
Gianni Sassanelli said: thanks Sagenut, Erel, DonManfred. i have corrected my paths as your suggestion. now i have the following configuration but SDK manager not work Click to expand... Do you are using the recommended SDK by Erel or only change the paths?
Gianni Sassanelli Active Member Licensed User Longtime User Aug 28, 2024 #11 asales said: Do you are using the recommended SDK by Erel or only change the paths? Click to expand... yes i have downloaded all files from recommended SDK and i have inserted it in new path Upvote 0
asales said: Do you are using the recommended SDK by Erel or only change the paths? Click to expand... yes i have downloaded all files from recommended SDK and i have inserted it in new path
asales Expert Licensed User Longtime User Aug 28, 2024 #12 Gianni Sassanelli said: yes i have downloaded all files from recommended SDK and i have inserted it in new path Click to expand... Maybe is better don't put the OpenJDK in the same path of the Android, like the link says "C:\java is a good place for it" Upvote 0
Gianni Sassanelli said: yes i have downloaded all files from recommended SDK and i have inserted it in new path Click to expand... Maybe is better don't put the OpenJDK in the same path of the Android, like the link says "C:\java is a good place for it"
Gianni Sassanelli Active Member Licensed User Longtime User Aug 28, 2024 #13 asales said: Maybe is better don't put the OpenJDK in the same path of the Android, like the link says "C:\java is a good place for it" View attachment 156437 Click to expand... i have copy and pasted in new location c:\JAVA but problem remain Upvote 0
asales said: Maybe is better don't put the OpenJDK in the same path of the Android, like the link says "C:\java is a good place for it" View attachment 156437 Click to expand... i have copy and pasted in new location c:\JAVA but problem remain
asales Expert Licensed User Longtime User Aug 28, 2024 #14 Gianni Sassanelli said: i have copy and pasted in new location c:\JAVA but problem remain Click to expand... I would try deleted the SDK and OpenJDK, download again and follow the instructions by Erel to install, using the 7-Zip and the recommended folders. Upvote 0
Gianni Sassanelli said: i have copy and pasted in new location c:\JAVA but problem remain Click to expand... I would try deleted the SDK and OpenJDK, download again and follow the instructions by Erel to install, using the 7-Zip and the recommended folders.
Gianni Sassanelli Active Member Licensed User Longtime User Aug 29, 2024 #15 SOLVED. The problem was due to the unzip of some folders that were not inserted in the correct path The Cmdline-Tools folder had not been decompressed, instead the two subfolders contained yes. thank's for all for the support. Upvote 0
SOLVED. The problem was due to the unzip of some folders that were not inserted in the correct path The Cmdline-Tools folder had not been decompressed, instead the two subfolders contained yes. thank's for all for the support.
