Create Android app stops at 60% (Solved)
Posted: Tue Sep 03, 2019 11:48 am
Just separated it from the similar IOS bug report since it seems to otherwise 'drown' in the IOS topic.
The problem is still present in Windows version. We have to revert to version 2.0 to compile to android aps.
Best regards
Peter
Update: 12/15/19.
Added this to the "tips and tricks" section too.
viewtopic.php?f=9&t=1478
This only concerns people using Windows 10 and Windows 10 Privacy Tool
available from this site: https://www.winprivacy.de/english-home/
Since SpiderBasic version 2.0, I have been unable to compile for
Android. An annoying crash happened each and every time at 60%.
No information, no hints and no way to explain why the compiler
stopped....Unable to give Fred any hints of ANY kind, I settled
for version 2.0 and did what I had to do..
Recently I bought new ssd drives, gfx card and other hardware which
required a completely new installation. Latest SpiderBasic and jdk installed
but this time I omitted the privacy tool...and there it was..!
Working like a charm. For the first time I was able to compile for Android
on a version greater then 2.0! Lovely!!
Now...Using a privacy tool can be a nice thing, but it does pose several
problems in doing so. At default settings, the privacy tool will
automatically tinker with telemetry and so forth....and this is some of the
issues that hinders the compiler from creating the Android app.
So...Be careful with privacy tools! It may be a great thing, but it can cause
problems in unexpected ways and become a real nuisance..
The problem is still present in Windows version. We have to revert to version 2.0 to compile to android aps.
Best regards
Peter
Update: 12/15/19.
Added this to the "tips and tricks" section too.
viewtopic.php?f=9&t=1478
This only concerns people using Windows 10 and Windows 10 Privacy Tool
available from this site: https://www.winprivacy.de/english-home/
Since SpiderBasic version 2.0, I have been unable to compile for
Android. An annoying crash happened each and every time at 60%.
No information, no hints and no way to explain why the compiler
stopped....Unable to give Fred any hints of ANY kind, I settled
for version 2.0 and did what I had to do..
Recently I bought new ssd drives, gfx card and other hardware which
required a completely new installation. Latest SpiderBasic and jdk installed
but this time I omitted the privacy tool...and there it was..!
Working like a charm. For the first time I was able to compile for Android
on a version greater then 2.0! Lovely!!
Now...Using a privacy tool can be a nice thing, but it does pose several
problems in doing so. At default settings, the privacy tool will
automatically tinker with telemetry and so forth....and this is some of the
issues that hinders the compiler from creating the Android app.
So...Be careful with privacy tools! It may be a great thing, but it can cause
problems in unexpected ways and become a real nuisance..