- Jun 6, 2020
- 11,593
- 4,507
I had to fix a small bug in my app, so I thought while I do it I'll update the targetSDK from 22 to 29, as Google requested.
Compiled, worked fine. Then I remember I had not updated my SDM in a while, so did so, and recompiled with android-29 instead of android-25.
App crashes on launch:
java.io.FileNotFoundException: /storage/emulated/0/SpiroConnect Mobile/settings.properties: open failed: EACCES (Permission denied)
So I read a bit about the issues that people have had with moving to android-29 and thought since I don't have muchtime now, just change back to android-25 and update the SDK another day. So I reverted to android-25, cleaned project, compiled and ran, and I get the same EACCES error that I have never seen before.
I wish I never touched it now, but I do need to get a working compilation done today.
So, is the introduction of the EACCES error due to the setting of targetSDK from 22 to 29, or was it because I updated the sdk from 25 to 29?
Many thanks
Compiled, worked fine. Then I remember I had not updated my SDM in a while, so did so, and recompiled with android-29 instead of android-25.
App crashes on launch:
java.io.FileNotFoundException: /storage/emulated/0/SpiroConnect Mobile/settings.properties: open failed: EACCES (Permission denied)
So I read a bit about the issues that people have had with moving to android-29 and thought since I don't have muchtime now, just change back to android-25 and update the SDK another day. So I reverted to android-25, cleaned project, compiled and ran, and I get the same EACCES error that I have never seen before.
I wish I never touched it now, but I do need to get a working compilation done today.
So, is the introduction of the EACCES error due to the setting of targetSDK from 22 to 29, or was it because I updated the sdk from 25 to 29?
Many thanks
برای دیدن لینک ها باید ثبت نام کنید