Your app is using a content provider with an unsafe implementation of openFile.

Solar2D General Questions/Discussion
#1

I got an alert recently from the Google Play Store Console:

Your app is using a content provider with an unsafe implementation of openFile. Please see this Google Help Center article for details.

What do i do?

#2

Never mind. I have to update Corona

#3

Thanks for posting back.  I saw the initial post and was thinking, “Man how do you deal with this…?”

#4

So i updated the app, did not change anything in the config, and updated the simulator. I uploaded it in the console and checked back in a few hours and i get an alert saying it still has the problem. i looked at a forum post regarding this and it says i have to wait for two days, and the alert dissapears. is that right?

#5

I downloaded and installed the 2017.3159 version of Corona SDK.

Then I re-built my app.

I published it at 08:52 and right now it’s 11:29 and the warning message is cleared.

Note: A second application was re-built the same way and published at 9:51 and the warning is still showing.

So I’m confident there is a time delay before the changes take effect.

#6

@Gary,

I’m going through the same wait, so I guess I’ll tell you when mine go away or not.

Cheers,

Ed

#7

It takes time for Google to update their display.  

Rob

#8

Yes, both of my apps have now cleared. Second one taking longer but it got there in the end :wink:

#9

Cleared.  Just one more to fix and I’ll be done with this fun.

#10

I am still waiting, the alert is still there.I updated it on October 23rd. Should I do another update?

#11

It wouldn’t hurt. You did push the change live?

Rob

#12

Gary I used 2017.3160 to resolve the issue.

#13

I made the previous versions on an old version of corona (a version back in may). I then downloaded the new version of corona. I haven’t updated it yet. If its still there, should I contact google?

#14

@garygusep2, you have to use a version of Corona 3160 or later, rebuild and resubmit your apps to Google to clear this error. It sounds like you have not done that (“I haven’t updated it yet”).

Rob

#15

I did update it on 3.160 on October 23rd. “I havent Updated it yet” meaning havent updated it the 3rd time.

#16

Well i feel stupid. The build i used to build the new version of my app is v 3135.

Im going to build it on the v 3160 now.

#17

Never mind. I have to update Corona

#18

Thanks for posting back.  I saw the initial post and was thinking, “Man how do you deal with this…?”

#19

So i updated the app, did not change anything in the config, and updated the simulator. I uploaded it in the console and checked back in a few hours and i get an alert saying it still has the problem. i looked at a forum post regarding this and it says i have to wait for two days, and the alert dissapears. is that right?

#20

I downloaded and installed the 2017.3159 version of Corona SDK.

Then I re-built my app.

I published it at 08:52 and right now it’s 11:29 and the warning message is cleared.

Note: A second application was re-built the same way and published at 9:51 and the warning is still showing.

So I’m confident there is a time delay before the changes take effect.