AppsGeyser Critical Notifications

⚠️⚠️⚠️Important!

If your app was removed from Google Play and you received an email exactly like the one in the attached screenshot above, please follow the steps to address the issue:

1️⃣ Make sure you have the correctly completed Data Safety section:
🔹Go to self-publish page for your app on AppsGeyser and download data safety file.
🔹Go to "App content" > "Data safety" on Developer Console.
🔹Click "Import from CSV and upload newly obtained data safety file.
🔹Save changes.

2️⃣ Make sure you have the newest version of AAB uploaded to Production:
🔹Rebuild your AAB.
🔹Go to "Production" > "Create new release" on Developer Console.
🔹Upload new AAB.

3️⃣ Proceed to "Publishing overview" section and submit your changes to review.

🔔 UPDATE: Wallpaper, Book Reader and Browser templates updated to align with Android 13 (API level 33). All new apps made on AppsGeyser now target API 33.

Please proceed to update your publications using our instructions to complete Advertising ID Declaration Form.

🔔 UPDATE: VPN Premium template updated to align with Android 13 (API level 33).

Please proceed to update your VPN Premium publications using our instructions to complete Advertising ID Declaration Form.

🔔 UPDATE: Chat AI template updated to align with Android 13 (API level 33).

Please proceed to update your Chat AI publications using our instructions to complete Advertising ID Declaration Form.

🔔 UPDATE: Media Player template updated to align with Android 13 (API level 33).

Please proceed to update your Media Player publications using our instructions to complete Advertising ID Declaration Form.

🔔 UPDATE: Store with Shopify template updated to align with Android 13 (API level 33).

Please proceed to update your Store with Shopify publications using our instructions to complete Advertising ID Declaration Form.

🔔 UPDATE: Messenger with Video Calls template updated to align with Android 13 (API level 33).

Please proceed to update your Messenger publications using our instructions to complete Advertising ID Declaration Form.

🔔 Attention, AppsGeyser Users!

We're excited to announce an essential update for all apps developed using the Business Website template. With our latest improvements, these apps are now aligned with Android 13 (API level 33).

Please follow these steps to update your publication:

1️⃣ Rebuild your AAB.

2️⃣ Visit your Developer Console, then go to "Production" > "Create new release" and upload new AAB.

3️⃣ On the next screen you will be prompted to fill in the Advertising ID Declaration Form, which is required for all apps targeting Android 13. Proceed to the form, select "Yes," and then choose the "Advertising or marketing" option. Save changes.

4️⃣ Proceed to "Publishing overview" section and submit your update to review.

It's crucial to implement these changes to ensure your app remains compatible with newer devices. Thank you for your prompt attention to this update.

For more detailed instructions please refer to our Knowledge Base article.

‼️Hello dear publishers and creators!

We're always looking for ways to improve. We invite you to help us learn about your experience by filling out this short survey. We promise it only takes a few minutes!

At the end of this survey, you will have a chance to be included in research interviews or chats with AppsGeyser product leaders that are held over video-conference.

If you are selected and do participate, you’ll be offered a $25 gift card as a thank you for your time!

If you're encountering the same issue with rejections but did not see the❗️UPDATE notification in this channel regarding your app's template (to determine which, please refer to our article), here's a solution:

1️⃣ Visit your Developer Console, go to "App content" > "Data Safety".

2️⃣ For the question "Is all of the user data collected by your app encrypted in transit?", select "No" and save changes.

3️⃣ Submit these changes for review in "Publishing overview" section.

🔔 Attention, app builders! Some of you might be getting "Invalid Encryption Declaration on your Data Safety form" rejections even after rebuilding your AAB and updating your publication as instructed.

We've identified a potential workaround:

1️⃣ Visit your Developer Console, then go to "App content" > "Data Safety". Change the answer to "Is all of the user data collected by your app encrypted in transit?" to "No", then save and submit this change for review in "Publishing overview" section.

2️⃣ After your changes have been accepted, rebuild your AAB and submit it as an update. Also, don't forget to do the same for all internal, open, and closed testing tracks you may have. Submit these changes for review.

3️⃣ Once your update is live, return to the "App content" > "Data Safety" section and revert the answer for "Is all of the user data collected by your app encrypted in transit?" back to "Yes". Then, submit this change for review.

While we hope this helps, please note that it may not work for everyone. Thanks for your patience and understanding, and don't hesitate to reach out for assistance!

Dear Publishers,

We want to bring to your attention some recent issues that have been reported with regards to data safety on Google Play. One of the main concerns has been around Invalid Encryption Declaration, which was fixed in the app rather than in Data Safety. As a result, all server requests are now being served via https, ensuring a higher level of data safety for your app users.

It's important to note that publishers need to update their aab file, not the Data Safety section, to ensure their app is compliant with these new data safety requirements. In some cases, Google Play may reject an update and provide old bundles as a reject reason. To resolve this issue, you will need to publish an update again.

We are aware that Google is currently asking for an advertising id declaration. Please note that this can be ignored for now, as it doesn't affect your publishing process. Additionally, Google may also be asking for an account creation declaration in the Data Safety section. While we are preparing a guide on how to complete this requirement, it can also be ignored for the time being.

To solve the current issues with Data Safety on Google Play, publishers must submit an updated aab file to the platform. We apologize for any inconvenience this may have caused and thank you for your patience and cooperation in ensuring the highest level of data safety for your app users.

❗️UPDATE: Photo Editor template source code updated and encrypted.

You need to:
1. Download updated .aab file for each app
2. Publish an update using our guide

❗️UPDATE: Media Player template source code updated and encrypted.

You need to:
1. Download updated .aab file for each app
2. Publish an update using our guide

❗️UPDATE: Browser template source code updated and encrypted.

You need to:
1. Download updated .aab file for each app
2. Publish an update using our guide

❗️UPDATE: Video Calls and Chat template source code updated and encrypted.

You need to:
1. Download updated .aab file for each app
2. Publish an update using our guide

❗️UPDATE: Wallpaper template source code updated and encrypted.

You need to:
1. Download updated .aab file for each app
2. Publish an update using our guide

❗️UPDATE: Store with Shopify template source code updated and encrypted.

You need to:
1. Download updated .aab file for each app
2. Publish an update using our guide

❗️UPDATE: Messenger with Video Calls and VPN Premium templates source codes updated and encrypted.

You need to:
1. Download updated .aab file for each app
2. Publish an update using our guide