LATEST: AppYet v4.2.6 Released

appyet

Support Team Member
Staff member
Hello All,

We have just released a new v4.0.20 with the following changes:

- Android: Removed "android.permission.REQUEST_INSTALL_PACKAGES" permission
- Android: Removed Web Module Download feature

This release we are again HOPING it will stop Google Play from false-positive the "Loan Download SDK", which AppYet has never used in the current or any previous version of our app template, neither AppYet created apps allow or support "modify, replace, or update itself using any method other than Google Play's update mechanism".

For people who have their app suspended, we are very concern and doing our best to investigate and help. But at this moment, the best you could do is contact Google Play support explain to them this is a false positive, hope they reverse App suspension.
 

srikanth

New Member
For example, your app (app version code 7) currently contains the following class, which contains code to download or install applications from unknown sources outside of Google Play:

  • com.download.library
If necessary, you can consult your SDK provider(s) for further information






Hi srikanth,



Thanks for your patience.

Status: App not available on Google Play, pending your action

I’m happy to report that we have conditionally accepted your appeal. I’ve included details below about what additional steps you’ll need to take to get your app,

Step 1: Update your app

During review, we found that your app causes users to download or install apps from unknown sources outside of Google Play, which is not compliant with our Device and Network Abuse policy:

  • An app distributed via Google Play may not modify, replace, or update itself using any method other than Google Play's update mechanism. Likewise, an app may not download executable code (e.g. dex, JAR, .so files) from a source other than Google Play. Please note that you are responsible for all aspects of your app; by using an SDK in your app, you are responsible for how that SDK behaves within your app.
  • Apps and app listings on Google Play must not provide any means to activate or access functionality that violate these terms, such as linking to a non-compliant APK hosted outside Google Play.
You can read through the Device and Network Abuse policy page for more details and examples of common violations.

For example, your app (app version code 7) currently contains the following class, which contains code to download or install applications from unknown sources outside of Google Play:

  • com.download.library
If necessary, you can consult your SDK provider(s) for further information.

To add, please make sure to deactivate the previous non-compliant version code (app version code 7) and increment the version code before submitting in your next submission. Note that all versions of your app should be compliant with our policies to prevent any future enforcements.


Additionally as a gentle reminder, please be advised that per the Repetitive Content policy, we don’t allow:

  • Creating multiple apps with highly similar functionality, content, and user experience. If these apps are each small in content volume, developers should consider creating a single app that aggregates all the content.
  • Please be aware that publishing identical content targeting the same locales is in violation of the Repetitive Content policy.
Please note that removal or administrative notices may not indicate each and every policy violation present in your app or broader app catalog. Developers are responsible for addressing any policy issue and conducting extra due diligence to ensure that the remainder of their apps are fully policy compliant. Failure to address policy violations in all of your apps may result in additional enforcement actions so we suggest that you review your catalog and take necessary actions to prevent further enforcement.

Please update your app to fix this issue. You may also want to double check that your app complies with all other Developer Program Policies, as additional enforcement could occur if there are further policy violations.

Step 2: Submit an update to your app

To submit an update to your app’s store listing information:

  1. Sign in to your Play Console.
  2. Select the app with the policy issue.
  3. Select Store presence > Main store listing.
  4. Make changes to bring your app into compliance.
  5. Click Save.
To submit an updated app bundle or APK:

  1. Prepare your updates.
  2. Create a new release using the compliant app bundle or APK. Be sure to create the new release on the same track(s) as the non-compliant app bundle or APK, increment the version number, and set the release to 100% rollout.
  3. Follow the on-screen instructions to add APKs or app bundles, then review and roll out your release.
If addressing the issue does not require a metadata or APK update and the submit button is grayed out, you can make a minor change to your store listing to activate the button. For example, add a space after your app title and then delete it. Once the button turns blue, you can submit your update.

Please note that after you submit an update to an existing app on your Play Console, it can take some time for your app to be processed for standard publishing on Google Play. To check your submission status, you may follow the steps below:

  1. Sign in to your Play Console.
  2. Select your app.
  3. On the left menu, select Release > Production or Testing (select the track(s) you have released)
If you're an AdMob publisher, please contact the AdMob team to re-enable ad serving.



Please let me know if you have any other questions. Thanks for your continued support of Google Play














Hello All,

We have just released a new v4.0.20 with the following changes:

- Android: Removed "android.permission.REQUEST_INSTALL_PACKAGES" permission
- Android: Removed Web Module Download feature

This release we are again HOPING it will stop Google Play from false-positive the "Loan Download SDK", which AppYet has never used in the current or any previous version of our app template, neither AppYet created apps allow or support "modify, replace, or update itself using any method other than Google Play's update mechanism".

For people who have their app suspended, we are very concern and doing our best to investigate and help. But at this moment, the best you could do is contact Google Play support explain to them this is a false positive, hope they reverse App suspension.
 

srikanth

New Member
Hello All,

We have just released a new v4.0.20 with the following changes:

- Android: Removed "android.permission.REQUEST_INSTALL_PACKAGES" permission
- Android: Removed Web Module Download feature

This release we are again HOPING it will stop Google Play from false-positive the "Loan Download SDK", which AppYet has never used in the current or any previous version of our app template, neither AppYet created apps allow or support "modify, replace, or update itself using any method other than Google Play's update mechanism".

For people who have their app suspended, we are very concern and doing our best to investigate and help. But at this moment, the best you could do is contact Google Play support explain to them this is a false positive, hope they reverse App suspension.
Google replay




Hi srikanth,



Thanks for your patience.

Status: App not available on Google Play, pending your action

I’m happy to report that we have conditionally accepted your appeal. I’ve included details below about what additional steps you’ll need to take to get your app,

Step 1: Update your app

During review, we found that your app causes users to download or install apps from unknown sources outside of Google Play, which is not compliant with our Device and Network Abuse policy:

  • An app distributed via Google Play may not modify, replace, or update itself using any method other than Google Play's update mechanism. Likewise, an app may not download executable code (e.g. dex, JAR, .so files) from a source other than Google Play. Please note that you are responsible for all aspects of your app; by using an SDK in your app, you are responsible for how that SDK behaves within your app.
  • Apps and app listings on Google Play must not provide any means to activate or access functionality that violate these terms, such as linking to a non-compliant APK hosted outside Google Play.
You can read through the Device and Network Abuse policy page for more details and examples of common violations.

For example, your app (app version code 7) currently contains the following class, which contains code to download or install applications from unknown sources outside of Google Play:

  • com.download.library
If necessary, you can consult your SDK provider(s) for further information.

To add, please make sure to deactivate the previous non-compliant version code (app version code 7) and increment the version code before submitting in your next submission. Note that all versions of your app should be compliant with our policies to prevent any future enforcements.


Additionally as a gentle reminder, please be advised that per the Repetitive Content policy, we don’t allow:

  • Creating multiple apps with highly similar functionality, content, and user experience. If these apps are each small in content volume, developers should consider creating a single app that aggregates all the content.
  • Please be aware that publishing identical content targeting the same locales is in violation of the Repetitive Content policy.
Please note that removal or administrative notices may not indicate each and every policy violation present in your app or broader app catalog. Developers are responsible for addressing any policy issue and conducting extra due diligence to ensure that the remainder of their apps are fully policy compliant. Failure to address policy violations in all of your apps may result in additional enforcement actions so we suggest that you review your catalog and take necessary actions to prevent further enforcement.

Please update your app to fix this issue. You may also want to double check that your app complies with all other Developer Program Policies, as additional enforcement could occur if there are further policy violations.

Step 2: Submit an update to your app

To submit an update to your app’s store listing information:

  1. Sign in to your Play Console.
  2. Select the app with the policy issue.
  3. Select Store presence > Main store listing.
  4. Make changes to bring your app into compliance.
  5. Click Save.
To submit an updated app bundle or APK:

  1. Prepare your updates.
  2. Create a new release using the compliant app bundle or APK. Be sure to create the new release on the same track(s) as the non-compliant app bundle or APK, increment the version number, and set the release to 100% rollout.
  3. Follow the on-screen instructions to add APKs or app bundles, then review and roll out your release.
If addressing the issue does not require a metadata or APK update and the submit button is grayed out, you can make a minor change to your store listing to activate the button. For example, add a space after your app title and then delete it. Once the button turns blue, you can submit your update.

Please note that after you submit an update to an existing app on your Play Console, it can take some time for your app to be processed for standard publishing on Google Play. To check your submission status, you may follow the steps below:

  1. Sign in to your Play Console.
  2. Select your app.
  3. On the left menu, select Release > Production or Testing (select the track(s) you have released)
If you're an AdMob publisher, please contact the AdMob team to re-enable ad serving.



Please let me know if you have any other questions. Thanks for your continued support of Google Play
 

appyet

Support Team Member
Staff member
Thank you @srikanth, this is exactly the detail we are looking for. This is very helpful.

We are double-checking the detail from Google Play, will respond to you very soon.
 

Alaa Ahmed

Active Member
Thank you @srikanth, this is exactly the detail we are looking for. This is very helpful.

We are double-checking the detail from Google Play, will respond to you very soon.
@appyet Will a new release be made within days? Do we update the applications to v4.0.20 or wait for the new version?
 
Last edited:

appyet

Support Team Member
Staff member
Hello all,

With detail from Google Play, We have released the latest update to fix the App Suspension issue. Please help test it and report back if any issues

4.0.21:
---------------------
- Android: Removed "android.permission.REQUEST_INSTALL_PACKAGES" permission
- Android: Removed Web Module Download feature (Removed com.download.library, which allows Web Module to download files if the link is to a file, it is a common and useful feature, but if it is misused and it is linked to a apk, it could trigger Google Play policy violations, which could result in app suspension)
 

MITS APP WORLD

New Member
@appyet I received this email from Google Support. It can be useful to find the issue.

--------------------------------------------------------------
Thanks for contacting the Google Play team.

During review, we found that your app, PNG News Feeds (mel.mitsapp.png.news.feeds.ky), causes users to download or install apps from unknown sources outside of Google Play, which is not compliant with our Device and Network Abuse policy:

  • An app distributed via Google Play may not modify, replace, or update itself using any method other than Google Play's update mechanism. Likewise, an app may not download executable code (e.g. dex, JAR, .so files) from a source other than Google Play. Please note that you are responsible for all aspects of your app; by using an SDK in your app, you are responsible for how that SDK behaves within your app.
  • Apps and app listings on Google Play must not provide any means to activate or access functionality that violate these terms, such as linking to a non-compliant APK hosted outside Google Play.
You can read through the Device and Network Abuse policy page for more details and examples of common violations.

For example, your app (app version code 59) is using a non-compliant version of Loan Download SDK which contains code to download or install applications from unknown sources outside of Google Play.

If necessary, you can consult your SDK provider(s) for further information.
 

rahul meena

New Member
We push out the 4.0.18 with the latest support libraries was hoping Google Play will stop false detect Load Download SDK.
which AppYet has never used in the current or any previous version of our app template, neither AppYet created apps allow or support "modify, replace, or update itself using any method other than Google Play's update mechanism".

For people who have their app suspended, we are very concern and doing our best to investigate and help. But at this moment, the best you could do is contact Google Play support explain to them this is a false positive, hope they reverse App suspension.

Unfortunately, at this moment, not much AppYet could do to help. We couldn't fix "Load Download SDK", since our app doesn't use it
One of my old app with v4.0.16 not suspended by Google. One year ago I had unpublished this app and yesterday I published this app without update and until now it's not suspended by Google maybe this information useful for study about app suspension.
 

Attachments

  • IMG_20210603_150302.jpg
    IMG_20210603_150302.jpg
    47 KB · Views: 16
  • IMG_20210603_150235.jpg
    IMG_20210603_150235.jpg
    58.7 KB · Views: 16

appyet

Support Team Member
Staff member
All V4 apps have com.download.library to allow web module download file from a web link. which triggers Google Play policy scan.
We strongly recommend everyone to rebuild your app with v4.0.21, test it thoroughly, then update your app with the latest version on Google Play, even for apps that don't have Web Module
 

appyet

Support Team Member
Staff member
For some of you like to know more detail about com.download.library, it is part of AgentWeb library (https://github.com/Justson/AgentWeb), it is a popular Web library used by many apps. It seems Google Play Policy scan doesn't look at details about how this library is used (eg. Allow user to download PDF file in web module), but it simply flags an app as a policy violation whenever this library is used.

Sadly, because of it we have to remove the download feature for the Web Module
 
Top