I updated three applications, but one security alert did not disappear.
It seems that it is included in one of the plugins.
How can I solve this?
< Google Play : Security alert >
Classes that contain vulnerabilities :
com.ansca.corona.storage.FileContentProvider
Due date :
01/15/2018
Screen shot :
What version of Corona are you using? We solved this problem a long time ago. The latest public release, which has many Google Play fixes and enhancements is version 3326 and will be required for new Google Play apps uploaded after August 1st.
If you’re not using 3326 or a daily build newer than that I would highly recommend updating as soon as you can.
Rob
Hello [member=‘Rob iracle’];
Yes I used Build:2018.3326.
I have built 3 Apps. The problem disappeared from 2 Apps.
But it will not disappear from the remaining 1 Apps.
I think that the difference is complexity and number of plug-ins.
First of all, is there a way to identify where the problem is?
How long has it been since you updated the one app that’s still flagged?
Until recently I used a old corona. Because my Xcode environment was old.
I have ignored the Android warning for a long time. 
I recently renewed my environment. And rebuilt the old app.
And the problem of the 2 apps went away last week.
The problem did not disappear from the last application I built a few days ago.
Although it is released to the current state store, it may be rejected. :unsure:
It could take a couple of days after updating before Google scans and clears the warning. There isn’t anything more than building with a newer version of Corona needed to fix the warning. Give it some more time. Then perhaps make sure you’ve released the latest build and Google Play doesn’t think you’re still on the older build.
Rob
Yes, I understand, I will wait until next week.
However, in another application, The caution mark was deleted at the same time as the release.
So I am worried…
I will post the results at a later date.
What version of Corona are you using? We solved this problem a long time ago. The latest public release, which has many Google Play fixes and enhancements is version 3326 and will be required for new Google Play apps uploaded after August 1st.
If you’re not using 3326 or a daily build newer than that I would highly recommend updating as soon as you can.
Rob
Hello [member=‘Rob iracle’];
Yes I used Build:2018.3326.
I have built 3 Apps. The problem disappeared from 2 Apps.
But it will not disappear from the remaining 1 Apps.
I think that the difference is complexity and number of plug-ins.
First of all, is there a way to identify where the problem is?
How long has it been since you updated the one app that’s still flagged?
Until recently I used a old corona. Because my Xcode environment was old.
I have ignored the Android warning for a long time.
I recently renewed my environment. And rebuilt the old app.
And the problem of the 2 apps went away last week.
The problem did not disappear from the last application I built a few days ago.
Although it is released to the current state store, it may be rejected. :unsure:
It could take a couple of days after updating before Google scans and clears the warning. There isn’t anything more than building with a newer version of Corona needed to fix the warning. Give it some more time. Then perhaps make sure you’ve released the latest build and Google Play doesn’t think you’re still on the older build.
Rob
Yes, I understand, I will wait until next week.
However, in another application, The caution mark was deleted at the same time as the release.
So I am worried…
I will post the results at a later date.