LATEST: AppYet v4.0.22 Released (Updated 2021-07-30)!!

carmen1977

New Member
Apps updated to version 4.0.18 ... ALL blocked !! always for the same reason: Loan Download SDK !! Unfortunately they have reset everything ...
 

appyet

Support Team Member
Staff 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
 

netudara

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
I think you are right.. This is google play issue.. Many developers accounts are terminated by google
This is tread - View: https://twitter.com/barisozaydinli/status/1399302453099651074


Baris Ozaydinli

@barisozaydinli


@GooglePlayDev
our developer account has been terminated out of blue & with no reason. We are Google Top Developer & our app has been featured among Best apps many times. We have been developing in the platform for 7 years and can’t get a human to tell us why this happened. Help!



@GooglePlayDev

·
3h

Replying to
@barisozaydinli
Hi Baris, sorry to hear that. I did a quick check on your case and it is currently handled by our relevant team. Due to the preventative measures being taken for our support specialists in light of COVID-19, it may take longer than usual to respond to your appeal request. [1/2]


Google Answear
Google Play Apps & Games

@GooglePlayDev


Replying to
@barisozaydinli
We are sorry for the inconvenience this may cause, and we appreciate your patience and understanding while our relevant team works on getting a response back to you as soon as possible. #AskPlayDev [2/2] Stay safe, Cansy
 

Eduardo

Member
Three more apps suspended, all with 4.0.18 version. All appealed but no answer on any of them from Google.
Also, the problem with one app that doesn't create the apk persists.
 

smartsoft

New Member
Old Mail from Google play :

From May 5, you will need to tell us why your app requires extended storage access

We have detected the requestLegacyExternalStorage flag in the manifest file of one or more of your app's app bundles or APKs.

Developers whose apps are running on Android 11 or later should make use of siled storage space so that users can better control access to their device's storage space. As of May 5, to offer your app on Android 11 or later, you will need to follow one of the procedures below:

Update your application to follow better privacy-friendly practices, for example using the Storage Access Framework or Media Store APIs
Update your application to declare the permission to access all files (MANAGE_EXTERNAL_STORAGE) in the manifest file, and complete the statement to allow access to all files in the Play Console from May 5th
Remove permission to access all files from your app
For apps targeting Android 11, the requestLegacyExternalStorage flag will be ignored. You must use the All Files Access permission to maintain extended access.

Apps that ask for permission to access all files when they are not allowed to do so will be removed from Google Play, and you will not be able to update them.
 

salah rayyan

New Member
The app was updated to version 4.0.18 and was accepted by Google Play, but the app was suspended after one day !
Has anyone here filed an appeal and it was accepted?
 

netudara

Member
Old Mail from Google play :

From May 5, you will need to tell us why your app requires extended storage access

We have detected the requestLegacyExternalStorage flag in the manifest file of one or more of your app's app bundles or APKs.

Developers whose apps are running on Android 11 or later should make use of siled storage space so that users can better control access to their device's storage space. As of May 5, to offer your app on Android 11 or later, you will need to follow one of the procedures below:

Update your application to follow better privacy-friendly practices, for example using the Storage Access Framework or Media Store APIs
Update your application to declare the permission to access all files (MANAGE_EXTERNAL_STORAGE) in the manifest file, and complete the statement to allow access to all files in the Play Console from May 5th
Remove permission to access all files from your app
For apps targeting Android 11, the requestLegacyExternalStorage flag will be ignored. You must use the All Files Access permission to maintain extended access.

Apps that ask for permission to access all files when they are not allowed to do so will be removed from Google Play, and you will not be able to update them.

Any one got their App Back after Appeal??
One app newly published.. Its ok...
 

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:
Top