Replies: 4 comments 3 replies
-
Are you using the AIR SDK Manager? If so, please open the Troubleshooting tab and run it again, and it should give some more details. Or, if you edit a file "c:\users\infos.airsdk\adt.cfg" and add a line This should indicate why it's falling back to the old mechanism. Likely causes might be:
thanks |
Beta Was this translation helpful? Give feedback.
-
Hello, Thank you for you reply.
Please note that the F:\ANDROID\SDK\ path is correct. Two things:
|
Beta Was this translation helpful? Give feedback.
-
So,
javac.exe is in the C:\Program Files\Java\jdk-11.0.17\bin folder My adt.cfg file: But the same issue remains... |
Beta Was this translation helpful? Give feedback.
-
OK, here is the log :
So, I could guess the issue is about the Android SDK.
And I left the AndroidPlatformSDK option in adt.cfg blank, since it was already set in the asconfig.json. Now, if I set AndroidPlatformSDK=F:/ANDROID/SDK in adt.cfg: So, we can say that the platformsdk setting in the asconfig.json doesn't work. Anyway, thank you very much for your precious help ! |
Beta Was this translation helpful? Give feedback.
-
Hi all,
While my application compiled perfectly, I suddenly got this error, for no apparent reason:
I saw this discussion:
#1782
So I'm very confused because I don't know why and where my application project suddenly jump to a legacy build method...
The only things I do is replacing a ANE in my lib folder and opening Android Studio...
Restoring the previous ANE did nothing.
How can I restore the correct build mode ?
Thank you for your help...
Beta Was this translation helpful? Give feedback.
All reactions