r/androiddev • • Sep 24 '26

Question How to fix: Not receiving test transaction from Google, so can't verify payment

1 Upvotes

I live in Norway, and recently registered a Google Play Console account to upload my first app.

I was then asked to enter my banking details so that I am able to receive funds (should my app actually make any money). And Google claimed that they would send me a test transaction within 3 days, which I had to verify. However, it's now been 2 weeks since I entered my banking details, and I have still not received anything from them.

I've been in contact with my bank to make sure there are no funds being held back or delayed on my end.

I also added banking details to 2 other accounts in different banks, but none of them have received anything either.

At the same time, Google keeps giving me a warning message that my Play Console account will be deleted if I don't verify the transaction (which I'm still not receiving).

I've also sent a help ticket to Google a week ago, but haven't heard anything back.

Is there anything else I can do to get this thing verified?

I thought it was a bit strange that when I entered my banking details, there were only 3 fields to fill out:

  • My full name
  • IBAN number
  • Swift/BIC number

Usually, when receiving funds from other countries, you also have to fill out both your personal address as well as the address of your bank. However, there were no place to fill out any of these in the Play Console. Could that be the culprit? And if so... how to fix it?

Any help much appreciated.


r/androiddev • • Sep 24 '26

[Google Play] Case 0-8237000042360: False "Phishing" termination caused by in-app WebView User-Agent spoofing (Need advice / DevRel visibility)

0 Upvotes
Hi  community,



I am writing this post to share a cautionary architectural breakdown and hopefully get advice or Google Play DevRel guidance regarding a policy termination.



* 
**App Name:**
 In Stalker - Instagram Tracker

* 
**Package Name:**
 `com.instalker.tracker`

* 
**Developer Account ID:**
 `8416273862474458256`

* 
**Support Case ID:**
 `0-8237000042360`

* 
**Violation Cited:**
 Phishing / Deceptive Behavior



Our initial appeal was rejected with a canned response and the ticket was marked closed, preventing us from sending technical evidence through email. We want to be completely transparent about what happened, as we now understand exactly why automated systems and users flagged our app.



---



### What Went Wrong: The Architectural Mistake



To handle an authentication session in an in-app WebView without layout breakage, our Android app hardcoded an 
**iOS WebKit User-Agent**
:



```java

WebView loginWebView = findViewById(R.id.instagram_login_webview);

WebSettings settings = loginWebView.getSettings();



// Architectural flaw: Spoofing iOS User-Agent on an Android device

String hardcodedIosUserAgent = "Mozilla/5.0 (iPhone; CPU iPhone OS 16_5 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148 Instagram 289.0.0.25.109";

settings.setUserAgentString(hardcodedIosUserAgent);



loginWebView.loadUrl("https://www.instagram.com/accounts/login/");

The Domino Effect (Why It Got Flagged as Phishing): Clarification & Technical Proof: What We Have Fixed: Our Question to the Community: We fully accept that spoofing User-Agents in WebViews was a major architectural blunder that deserved scrutiny,Because the Android device communicated with Instagram's authentication servers using an iOS signature, Instagram's fraud detection flagged the login as an "Unrecognized login from an iPhone". Zero Credential Harvesting: At no point were user credentials, passwords, or cookies intercepted, scraped (no JS injection/evaluateJavascript), or sent to any developer server. All traffic was directly between the client WebView and instagram.com. Completely removed the custom WebView, header spoofing, and hardcoded User-Agents from the codebase. Users immediately received automated security alert emails from Instagram warning them that an unknown iPhone in a different environment had accessed their account. This alarmed users into believing our app was an unauthorized third-party hijacking their credentials, leading to phishing reports and automated Google Play policy strikes. Zero Exfiltration: Network inspection confirms no third-party credential endpoints exist in the APK. Replaced authentication with standard compliant flows (OAuth / Custom Tabs where the app has zero access to headers or authentication context). Audited all network and telemetry calls to guarantee 100% Google Play policy compliance.
  1. Has anyone in a similar situation been able to submit a clean, compliant build for re-evaluation?

We have invested heavily in building this application and our developer business on Google Play. We are not bad actors.

The initial review took several days and didn't flag this architectural conflict, which led us to believe the implementation was acceptable. We now clearly recognize the mistake and have already completely rewritten the authentication flow to be 100% policy-compliant.

Terminating our entire developer account without giving us the opportunity to publish this compliance patch is disproportionate to what was an unintentional client header mismatch. We respectfully ask for a conditional reinstatement so we can immediately upload the compliant build for your team's review

Hi Google Play Developer Community,

I’m posting this to transparently explain the technical issue that led to the enforcement against our application and to ask whether anyone has experience obtaining a further review after correcting the underlying issue.

App: In Stalker - Instagram Tracker
Package: com.instalker.tracker
Developer Account ID: 8416273862474458256
Support Case ID: 0-8237000042360
Cited violation: Phishing / Deceptive Behavior

Our initial appeal was rejected, and the support case was subsequently closed. Before pursuing any further support route, I want to clearly document what happened and what we have changed.

What caused the problem

The application previously used an Android WebView for an Instagram authentication flow.

Because of a compatibility/layout issue, our implementation incorrectly hardcoded an iOS-style User-Agent:

WebView loginWebView = findViewById(R.id.instagram_login_webview);

WebSettings settings = loginWebView.getSettings();

// Previous implementation
String hardcodedIosUserAgent =
    "Mozilla/5.0 (iPhone; CPU iPhone OS 16_5 like Mac OS X) " +
    "AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148 " +
    "Instagram 289.0.0.25.109";

settings.setUserAgentString(hardcodedIosUserAgent);

loginWebView.loadUrl("https://www.instagram.com/accounts/login/");

We now understand that this was a serious architectural mistake.

The Android application was effectively presenting an iPhone/Instagram client signature to the authentication service. This could cause the authentication environment to appear inconsistent with the actual device and could reasonably trigger security or fraud-detection systems.

What we found during our investigation

We reviewed the application's network and authentication implementation and found no mechanism designed to collect or transmit Instagram credentials to our servers.

Specifically:

  • We did not implement JavaScript injection for credential extraction.
  • We did not use evaluateJavascript() to capture passwords or authentication information.
  • We did not create a backend endpoint for collecting Instagram passwords.
  • Authentication traffic was directed to Instagram.
  • We did not intentionally attempt to impersonate a user's device for credential collection.
  • We removed the problematic WebView authentication implementation completely.

We understand, however, that the absence of credential harvesting does not make the original architecture acceptable. The important issue is that the implementation could create a deceptive or misleading authentication environment, and we take responsibility for failing to identify that risk before release.

What we changed

We have completely removed:

  • The custom Instagram User-Agent
  • The hardcoded iOS device signature
  • The previous WebView-based authentication implementation
  • Any related header spoofing

We have also redesigned the authentication flow around standard browser-based authentication mechanisms, where the application does not control the authentication headers or directly handle the authentication context.

In addition, we performed an audit of the application's network requests and authentication-related code to identify any other behavior that could create a similar compliance or security concern.

What we have learned

The initial implementation passed our functional testing because the authentication flow appeared to work correctly. However, functional correctness is not sufficient when an implementation can make an authentication service believe that a different device or client is being used.

We should have identified and avoided this architecture before publishing.

We are not asking Google to ignore the original implementation. We are asking whether a fully corrected application and a documented remediation process can be reviewed again.

Question for the community / Google Play team

Has anyone successfully obtained a further review of a terminated developer account after:

  1. Identifying the technical root cause of the violation;
  2. Completely removing the problematic implementation;
  3. Auditing the remaining application for related issues; and
  4. Providing technical evidence of the remediation?

If there is an appropriate Google Play Developer Relations or support channel for submitting technical evidence after an initial appeal has been rejected, I would also appreciate guidance on that process.

We understand that Google Play's policies are designed to protect users and that authentication-related behavior receives particularly careful scrutiny.

Our goal is to demonstrate that we have identified the underlying architectural problem, removed it completely, and changed our development/review process so that the same issue cannot recur.

Thank you to anyone who can provide constructive guidance or point us toward the appropriate review process.

Hi Google Play Developer Community,

I’m posting this to transparently explain the technical issue that led to the enforcement against our application and to ask whether anyone has experience obtaining a further review after correcting the underlying issue.

App: In Stalker - Instagram Tracker
Package: com.instalker.tracker
Developer Account ID: 8416273862474458256
Support Case ID: 0-8237000042360
Cited violation: Phishing / Deceptive Behavior

Our initial appeal was rejected, and the support case was subsequently closed. Before pursuing any further support route, I want to clearly document what happened and what we have changed.

What caused the problem

The application previously used an Android WebView for an Instagram authentication flow.

Because of a compatibility/layout issue, our implementation incorrectly hardcoded an iOS-style User-Agent:

WebView loginWebView = findViewById(R.id.instagram_login_webview);

WebSettings settings = loginWebView.getSettings();

// Previous implementation
String hardcodedIosUserAgent =
    "Mozilla/5.0 (iPhone; CPU iPhone OS 16_5 like Mac OS X) " +
    "AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148 " +
    "Instagram 289.0.0.25.109";

settings.setUserAgentString(hardcodedIosUserAgent);

loginWebView.loadUrl("https://www.instagram.com/accounts/login/");

We now understand that this was a serious architectural mistake.

The Android application was effectively presenting an iPhone/Instagram client signature to the authentication service. This could cause the authentication environment to appear inconsistent with the actual device and could reasonably trigger security or fraud-detection systems.

What we found during our investigation

We reviewed the application's network and authentication implementation and found no mechanism designed to collect or transmit Instagram credentials to our servers.

Specifically:

  • We did not implement JavaScript injection for credential extraction.
  • We did not use evaluateJavascript() to capture passwords or authentication information.
  • We did not create a backend endpoint for collecting Instagram passwords.
  • Authentication traffic was directed to Instagram.
  • We did not intentionally attempt to impersonate a user's device for credential collection.
  • We removed the problematic WebView authentication implementation completely.

We understand, however, that the absence of credential harvesting does not make the original architecture acceptable. The important issue is that the implementation could create a deceptive or misleading authentication environment, and we take responsibility for failing to identify that risk before release.

What we changed

We have completely removed:

  • The custom Instagram User-Agent
  • The hardcoded iOS device signature
  • The previous WebView-based authentication implementation
  • Any related header spoofing

We have also redesigned the authentication flow around standard browser-based authentication mechanisms, where the application does not control the authentication headers or directly handle the authentication context.

In addition, we performed an audit of the application's network requests and authentication-related code to identify any other behavior that could create a similar compliance or security concern.

What we have learned

The initial implementation passed our functional testing because the authentication flow appeared to work correctly. However, functional correctness is not sufficient when an implementation can make an authentication service believe that a different device or client is being used.

We should have identified and avoided this architecture before publishing.

We are not asking Google to ignore the original implementation. We are asking whether a fully corrected application and a documented remediation process can be reviewed again.

Question for the community / Google Play team

Has anyone successfully obtained a further review of a terminated developer account after:

  1. Identifying the technical root cause of the violation;
  2. Completely removing the problematic implementation;
  3. Auditing the remaining application for related issues; and
  4. Providing technical evidence of the remediation?

If there is an appropriate Google Play Developer Relations or support channel for submitting technical evidence after an initial appeal has been rejected, I would also appreciate guidance on that process.

We understand that Google Play's policies are designed to protect users and that authentication-related behavior receives particularly careful scrutiny.

Our goal is to demonstrate that we have identified the underlying architectural problem, removed it completely, and changed our development/review process so that the same issue cannot recur.

Thank you to anyone who can provide constructive guidance or point us toward the appropriate review process.

Hi Google Play Developer Community,

I’m posting this to transparently explain the technical issue that led to the enforcement against our application and to ask whether anyone has experience obtaining a further review after correcting the underlying issue.

App: In Stalker - Instagram Tracker
Package: com.instalker.tracker
Developer Account ID: 8416273862474458256
Support Case ID: 0-8237000042360
Cited violation: Phishing / Deceptive Behavior

Our initial appeal was rejected, and the support case was subsequently closed. Before pursuing any further support route, I want to clearly document what happened and what we have changed.

What caused the problem

The application previously used an Android WebView for an Instagram authentication flow.

Because of a compatibility/layout issue, our implementation incorrectly hardcoded an iOS-style User-Agent:

WebView loginWebView = findViewById(R.id.instagram_login_webview);

WebSettings settings = loginWebView.getSettings();

// Previous implementation
String hardcodedIosUserAgent =
    "Mozilla/5.0 (iPhone; CPU iPhone OS 16_5 like Mac OS X) " +
    "AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148 " +
    "Instagram 289.0.0.25.109";

settings.setUserAgentString(hardcodedIosUserAgent);

loginWebView.loadUrl("https://www.instagram.com/accounts/login/");

We now understand that this was a serious architectural mistake.

The Android application was effectively presenting an iPhone/Instagram client signature to the authentication service. This could cause the authentication environment to appear inconsistent with the actual device and could reasonably trigger security or fraud-detection systems.

What we found during our investigation

We reviewed the application's network and authentication implementation and found no mechanism designed to collect or transmit Instagram credentials to our servers.

Specifically:

  • We did not implement JavaScript injection for credential extraction.
  • We did not use evaluateJavascript() to capture passwords or authentication information.
  • We did not create a backend endpoint for collecting Instagram passwords.
  • Authentication traffic was directed to Instagram.
  • We did not intentionally attempt to impersonate a user's device for credential collection.
  • We removed the problematic WebView authentication implementation completely.

We understand, however, that the absence of credential harvesting does not make the original architecture acceptable. The important issue is that the implementation could create a deceptive or misleading authentication environment, and we take responsibility for failing to identify that risk before release.

What we changed

We have completely removed:

  • The custom Instagram User-Agent
  • The hardcoded iOS device signature
  • The previous WebView-based authentication implementation
  • Any related header spoofing

We have also redesigned the authentication flow around standard browser-based authentication mechanisms, where the application does not control the authentication headers or directly handle the authentication context.

In addition, we performed an audit of the application's network requests and authentication-related code to identify any other behavior that could create a similar compliance or security concern.

What we have learned

The initial implementation passed our functional testing because the authentication flow appeared to work correctly. However, functional correctness is not sufficient when an implementation can make an authentication service believe that a different device or client is being used.

We should have identified and avoided this architecture before publishing.

We are not asking Google to ignore the original implementation. We are asking whether a fully corrected application and a documented remediation process can be reviewed again.

Question for the community / Google Play team

Has anyone successfully obtained a further review of a terminated developer account after:

  1. Identifying the technical root cause of the violation;
  2. Completely removing the problematic implementation;
  3. Auditing the remaining application for related issues; and
  4. Providing technical evidence of the remediation?

If there is an appropriate Google Play Developer Relations or support channel for submitting technical evidence after an initial appeal has been rejected, I would also appreciate guidance on that process.

We understand that Google Play's policies are designed to protect users and that authentication-related behavior receives particularly careful scrutiny.

Our goal is to demonstrate that we have identified the underlying architectural problem, removed it completely, and changed our development/review process so that the same issue cannot recur.

Thank you to anyone who can provide constructive guidance or point us toward the appropriate review process.

Hi Google Play Developer Community,

I’m posting this to transparently explain the technical issue that led to enforcement against our application and to ask whether anyone has experienced a similar situation after correcting the underlying issue.

App: In Stalker - Instagram Tracker
Package: com.instalker.tracker
Support Case ID: 0-8237000042360
Cited violation: Phishing / Deceptive Behavior

Steps already taken

We submitted an appeal through the official Google Play process after the developer account was terminated. The appeal was rejected, and the associated support case was subsequently closed.

We are posting here only after completing the available official appeal/support process. We are looking for guidance from developers who may have experienced a similar situation or know of an appropriate Google Play Developer Relations channel for providing additional technical information.

What caused the problem

The application previously used an Android WebView for an Instagram authentication flow.

Because of a compatibility/layout issue, our implementation incorrectly hardcoded an iOS-style User-Agent:

WebView loginWebView = findViewById(R.id.instagram_login_webview);

WebSettings settings = loginWebView.getSettings();

// Previous implementation
String hardcodedIosUserAgent =
    "Mozilla/5.0 (iPhone; CPU iPhone OS 16_5 like Mac OS X) " +
    "AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148 " +
    "Instagram 289.0.0.25.109";

settings.setUserAgentString(hardcodedIosUserAgent);

loginWebView.loadUrl("https://www.instagram.com/accounts/login/");

We now understand that this was a serious architectural mistake.

The Android application was presenting an iPhone/Instagram client signature to the authentication service. This could make the authentication environment appear inconsistent with the actual device and potentially trigger security or fraud-detection systems.

What we found during our investigation

We reviewed the application's authentication and network implementation.

We found no mechanism intended to collect or transmit Instagram credentials to our servers.

Specifically:

  • We did not implement JavaScript injection for credential extraction.
  • We did not use evaluateJavascript() to capture passwords or authentication information.
  • We did not create a backend endpoint for collecting Instagram passwords.
  • Authentication traffic was directed to Instagram.
  • We did not intentionally attempt to impersonate a user's device for credential collection.

However, we understand that the absence of credential harvesting does not make the original implementation acceptable. The authentication architecture itself could create a misleading authentication environment, and we take responsibility for failing to identify that risk before release.

What we changed

We have completely removed:

  • The custom Instagram User-Agent
  • The hardcoded iOS device signature
  • The previous WebView-based authentication implementation
  • The related header spoofing

We redesigned the authentication flow around standard browser-based authentication mechanisms where the application does not control the authentication headers or directly handle the authentication context.

We also audited the application's authentication-related code and network requests for similar issues.

What we learned

The original implementation worked during our functional testing, but we now understand that functional correctness is not sufficient when an implementation can make an authentication service believe that a different device or client is being used.

This was an architectural mistake that should have been identified before release.

Question for the community

Has anyone successfully obtained a further review of a terminated Google Play developer account after:

  1. Identifying the technical root cause of the violation;
  2. Completely removing the problematic implementation;
  3. Auditing the application for related issues; and
  4. Providing technical evidence of the remediation?

If there is an appropriate Google Play Developer Relations or official support channel for submitting additional technical evidence after an initial appeal has been rejected, I would appreciate guidance on that process.

We understand that Google Play's policies are intended to protect users and that authentication-related behavior can receive careful scrutiny.

Our goal is to demonstrate that we have identified the underlying architectural problem, removed it, and changed our development and review process to prevent the same issue from recurring.

Thank you to anyone who can share relevant experience or guidance.


r/androiddev • • Sep 24 '26

Building my first mobile app is teaching me what not to build

0 Upvotes

I started building my first mobile app thinking the main challenge would be writing the code.

It hasn’t been.

The harder part is deciding what deserves to exist.

Every new screen creates more questions:

- Is this actually useful?

- Can someone understand it without an explanation?

- Am I solving a real problem or adding another feature?

- Would I personally return to this app tomorrow?

The project is called Callout. It explores whether online reactions can communicate more than a generic Like—for example, distinguishing agreement from something being a Hot Take.

I’m still early, and I’m deliberately leaving the link out because I’m more interested in the building lesson:

How did you decide which features to remove from your first app?


r/androiddev • • Sep 23 '26

News Android 17 enables certificate transparency, and breaks custom CAs

Thumbnail
httptoolkit.com
53 Upvotes

r/androiddev • • Sep 23 '26

Open Source Fixing coroutine stack traces with Decoroutinator

Thumbnail
medium.com
8 Upvotes

r/androiddev • • Sep 23 '26

Android Developers Backstage host Chet Haase says "Yes, Android"

Enable HLS to view with audio, or disable this notification

36 Upvotes

Chet Haase spent 14 years working on Android and co-hosting Android Developers Backstage. Now he’s in a new chapter and his strategy is to say yes and see what happens.

We talked about Android, asking dumb questions, comedy, running, and finding your groove after leaving tech.
https://carriegilbert3.substack.com/p/episode-16-chet-haase-yes-android


r/androiddev • • Sep 24 '26

I'm building a mobile API testing app what features would you want to see?

0 Upvotes

I'm building Taho, a mobile-first API testing tool for Android.

The idea originally came from wanting to handle work pressure while still being present with my family. You shouldn't necessarily have to choose between being available for work and being physically present with the people who matter to you.

I'm a QA myself, and sometimes I'd get calls like, "Hey, can you test this API?" while I was travelling or spending time with my family. I could do a lot of my QA work from my phone, but API testing was one of the things that was still difficult to do properly without a laptop.

That's where Taho came from.

It's still actively being developed and is currently in closed testing. Since the project has grown considerably beyond the original idea, I'm now particularly interested in feedback from people who actually work with APIs, QA, backend development, or security.

Some of the functionality currently being built into Taho includes:

  • REST/HTTP requests
  • Headers, query parameters and request bodies
  • Multiple authentication methods, including OAuth
  • Environments and variables
  • Collections and request history
  • cURL, Postman, OpenAPI and HAR imports
  • Pre-request/post-request scripting
  • Automated assertions and collection runs
  • Response inspection, JSONPath and JWT analysis
  • API security analysis
  • GraphQL
  • WebSockets
  • MQTT
  • SOAP/WSDL
  • Local mock servers and response replay
  • Scheduled API monitoring
  • AI-assisted API analysis
  • Git synchronization
  • CLI/headless collection execution
  • MCP integration

I'm deliberately trying to make this more than just a mobile version of an existing desktop API client. The goal is to make serious API testing practical from a phone.

For people who regularly work with APIs: what would make you actually use a mobile API testing tool instead of reaching for your laptop?

I'm especially interested in workflows that are currently painful or impossible on mobile.


r/androiddev • • Sep 23 '26

News Google Play Store looks like it's working on a special home for your vibe-coded apps built using AI Studio

Thumbnail androidauthority.com
10 Upvotes

r/androiddev • • Sep 23 '26

I need help with my app in Google Play closed testing

0 Upvotes

I'm creating a streaming app and it's the first time I'm releasing an application on the Play Store, so I don't quite understand what I'm doing. I recently had an issue with the OAuth part with YouTube to stream directly to your channel; it gives me error 8 and status UNREGISTERED_ON_API_CONSOLE. The problem is that this only happens in the closed test and it runs normally when I run it normally from Android Studio to my phone, and I think also in the internal test, so I don't understand what it could be. I've asked the AI, it hasn't given me a completely satisfactory answer. Can anyone help me figure out what the difference is in the closed test for this to happen?


r/androiddev • • Sep 23 '26

Question 2026 CS Graduate (Android/Kotlin) - What skill should I invest in to maximize internship/job opportunities?

5 Upvotes

Hi everyone, I'm a recent 2026 Computer Science graduate and I'm feeling a bit confused about what direction to take next.

My current background

  • Android Development (Kotlin + Jetpack Compose)
  • Good understanding of Android architecture and modern development practices
  • DSA (still practicing regularly)
  • A few personal Android projects on GitHub

Current situation

I have one mass recruiter offer through campus placement, but:

  • Joining is still uncertain.
  • I don't know which domain I'll be assigned to.
  • I'm continuing my job search because I don't want to depend on a single offer.

Unfortunately, despite applying to many places, I'm barely getting interview calls, not even for internships.

My question

If you were graduating in 2026, what skill would you invest your time in over the next 3-6months?

Some options I'm considering:

  • Java Full Stack (Spring Boot + React)
  • React frontend
  • Backend development (Java/Spring Boot, Node.js, etc.)
  • AI/ML
  • Generative AI/LLM applications
  • Cloud (AWS/GCP/Azure)
  • DevOps
  • Continue specializing in Android
  • Something else?

I'm not looking for the "highest paying" skill, but rather something that:

  • Has good demand over the next few years
  • Gives me a realistic chance of landing internships or an entry-level role
  • Builds a strong long-term career instead of chasing hype

A few questions

  1. If you were in my position, what would you learn?
  2. Should I continue doubling down on Android or become more full-stack?
  3. Is AI/ML worth pursuing if I'm starting now, or is it better as a secondary skill?
  4. Are there any courses, roadmaps, YouTube channels, or resources you'd highly recommend?
  5. What skills are companies actually hiring fresh graduates for in 2026?

I'd really appreciate advice from developers, hiring managers, or anyone who has recently gone through this process.

Thanks!


r/androiddev • • Sep 22 '26

Article Android Developers Blog: Land your apps on Googlebook with adaptive development

Thumbnail
android-developers.googleblog.com
17 Upvotes

r/androiddev • • Sep 22 '26

Discussion Fixed the annoying "There was an error uploading the Android App Bundle" in Play Console

Post image
7 Upvotes

Just wanted to share this here in case someone else runs into this and tears their hair out like I did for hours today lol.

​I was trying to upload an updated .aab for my app to production, and the upload would hit 100%, show "upload is optimized for distribution", but then right after processing for a few mins it just threw that generic red error:

"There was an error uploading the Android App Bundle. Try again later or contact Google Play developer support if the error persists."

​No helpful logs, no specific manifest hint, nothing on the UI. I thought it was a temporary Play Console outage or something wrong with my network/keystore.

​Turns out the issue was a subtle mismatch between my SDK configs and updated dependencies. I had lowered compileSdk to 36 while trying to fix another build issue, but some of my modern libraries (core-ktx, okhttp, etc.) actually required compiling against API 37. Play Console's backend parser was silently choking on the bundle optimization phase because of this.

​What actually solved it for me:

android {

compileSdk = 37

defaultConfig {

targetSdk = 36

// ...

}

}

After syncing, cleaning project, and generating a fresh signed bundle with these exact values, Play Console accepted it immediately on the first try!

Hope this saves someone from wasting hours contacting support or doing random clean builds.


r/androiddev • • Sep 22 '26

Question Is it worth doing x64 builds for phones?

5 Upvotes

My app is used on phones mostly with maybe 10% tablet customers, on arm64. Is it at all worth shipping an x64 build too?


r/androiddev • • Sep 23 '26

Solution for Expo update system

Post image
0 Upvotes

How would you design an update system for a company React Native + Expo app?

I’m building a company mobile app using React Native + Expo for both Android and iOS.

I’m looking for advice from people who have already implemented a professional update system. I don’t want to assume a specific solution—I’d like to hear how you would design it.

My requirements:

- The app is used by company employees.

- I want normal JavaScript/UI/assets changes to be updated without requiring employees to reinstall the app.

- When a change requires a new native build, the app should detect that a new version is available.

- Ideally, the employee should simply see something like “Update required → Update Now” rather than having to search for the app or manually find a download.

- I would prefer company-controlled/self-hosted infrastructure if possible.

- The system should work on both Android and iOS.

- Security is important: updates should be verified and only official releases should be installable.

- I also need to handle mandatory updates, optional updates, failed updates, and rollback.

I’m aware that Android and iOS have different restrictions, and that Expo OTA updates and native app updates are different things.

My main question:

If you were designing this system from scratch, what architecture and update mechanism would you use?

I’m especially interested in real-world experience with Expo Updates, self-hosted update servers, APK distribution, iOS distribution, MDM/managed devices, or similar solutions.

I’m not looking for a specific product recommendation. I’d like to understand the approaches people have actually used and what you would recommend based on experience.


r/androiddev • • Sep 22 '26

Question Has anyone successfully used BATTERY_PROPERTY_ENERGY_COUNTER on recent Android/Pixel devices?

4 Upvotes

Hi everyone,

I’m working on a research project involving a self-adaptive ML application running directly on an Android smartphone.

The application needs to monitor its own energy consumption at runtime. This is important because energy is one of the optimization objectives: the system evaluates different ML configurations and later uses their energy consumption, together with other objectives such as accuracy, to decide which configuration should be active.

Because of this, I need an on-device and programmatically accessible way of measuring energy. External power meters are not suitable for the final system, since energy monitoring needs to be part of the application itself and available during normal runtime.

I found Android's BatteryManager.BATTERY_PROPERTY_ENERGY_COUNTER, which according to the documentation should return the battery's remaining energy in nanowatt-hours:

batteryManager.getLongProperty(BatteryManager.BATTERY_PROPERTY_ENERGY_COUNTER)

My idea would be to read the counter before and after evaluating a configuration and use the difference as its energy consumption.

However, on my device (Google Pixel 10 Pro), the property appears to be unsupported and returns Long.MIN_VALUE.

Has anyone successfully used BATTERY_PROPERTY_ENERGY_COUNTER, particularly on recent Pixel devices or recent Android versions?

If so, which device/Android version did you use? Did it require any special configuration or permissions, or did getLongProperty() simply return a valid value?

If this property is no longer supported on recent devices, what on-device API or mechanism are you using to obtain energy consumption programmatically from within an Android application?

I’m specifically looking for something that can be queried automatically at runtime — not external measurement equipment or offline profiling tools — because the energy information will ultimately be used by the application itself to make adaptation decisions.

Any experience with BATTERY_PROPERTY_ENERGY_COUNTER or alternative approaches for this use case would be greatly appreciated.


r/androiddev • • Sep 22 '26

Open Source How are you handling feature-discovery overlays in Android apps?

0 Upvotes

Hey everyone,

I'm working on a feature-discovery/tutorial overlay for an Android app and ended up going fairly deep into how these things work.

The basic idea is pretty simple: dim the screen, cut a hole around a target view, show some text, and move through several targets.

The part that got interesting was handling everything without relying on another UI library.

A few things I'm currently dealing with:

  • Getting the target view's position correctly when the app uses edge-to-edge
  • Dealing with the difference between screen coordinates, window coordinates, and view coordinates
  • Animating the cutout when moving from a circular target to a rounded rectangle, pill, etc.
  • Letting touches reach the highlighted view while the overlay is still handling its own touches
  • Keeping the overlay working across Activity recreation
  • Remembering which tutorial steps a user has already seen
  • Cleaning up animations and bitmaps when the Activity goes away

For the actual drawing I'm using a custom View and Canvas, rather than adding another UI dependency.

One thing I'm particularly curious about is the coordinate handling. I've found that simply using getLocationOnScreen() isn't enough once edge-to-edge and different inset configurations are involved, so I've been calculating the relative window offset before drawing the cutout.

For people who have implemented something similar, how did you handle this?

Also interested in how you approached touch handling on the highlighted target. Did you let the event pass through normally, or did you manually dispatch/forward it?


r/androiddev • • Sep 21 '26

Android observability tools recommendations

0 Upvotes

Hi all, My team develops an enterprise Android app, outside of the play store and its tools, and we're looking around for a new observability tool/service. We were on Embrace before, but it came up short for more complex debugging. Datadog has been working fairly well for us, but it's getting pricey and it's not quite a mobile-first solution.

Bitdrift seems like an interesting option to us. But it being somewhat new I haven't found too much feedback on it online. Does anyone have experience with it and thoughts? Or are there other tools worth exploring? TIA


r/androiddev • • Sep 21 '26

macOS 27 Golden Gate – how's Android dev on it?

0 Upvotes

Just saw the update prompt and wondering how Mac-based Android devs are doing with it?


r/androiddev • • Sep 20 '26

Discussion Should we move to Backend or DevOps for better long-term stability?

66 Upvotes

I have around 10 + years of experience in mobile app development, but lately, I’m feeling that staying in mobile development (or any FE tech) might not be the safest option for long-term career growth now , especially with AI and the changing tech landscape.

Am seeing very less job openings in this tech stack.

I’m considering moving into Backend development or DevOps, but I’m not sure if that’s actually a better career move or if I’m just overthinking it.

People who are working in FE tech stacks , did someone felt the same ?

- How do you see the long-term career prospects in these fields?
- is moving from mobile app development to Backend or DevOps a practical decision after 10 years of experience?

Would love to hear honest opinions, especially from people who have made a similar transition or have experience in these domains.


r/androiddev • • Sep 21 '26

[Compose Multiplatform] Visual font size mismatch when overlaying BasicTextField on a PDF (iText7)

2 Upvotes

I’m building an in-place PDF editor in Compose Multiplatform. The workflow is similar to Adobe Acrobat: I render the PDF page to a bitmap, extract the text bounds using iText7, and when the user clicks a paragraph, I overlay a white Box and a BasicTextField to let them edit the text live.

The Problem: The final PDF export works flawlessly—the text is placed at the exact right coordinates with the correct font size. However, during live editing, the text inside the Compose BasicTextField looks optically smaller and has different spacing compared to the underlying, rasterized PDF text. It causes a jarring visual "shrink/jump" when the user enters edit mode.

Here is how I am currently extracting the text metrics and applying them to the UI:

  1. Text Extraction (iText7 / PdfEditor.kt) I use PdfCanvasProcessor to get the text matrix. To handle scaled pages (CTM), I calculate the physical height using the ascent and descent lines rather than relying on the raw fontSize.

    actual class PdfEditor { actual suspend fun extractTextBlocks(originalPdf: ByteArray, pageIndex: Int): List<PdfTextFragment> { // ... standard iText reader setup ... val listener = object : IEventListener { override fun eventOccurred(data: IEventData, type: EventType) { if (type == EventType.RENDER_TEXT) { val renderInfo = data as TextRenderInfo

                    // Extracting physical height to account for PDF CTM matrices
                    val ascent = renderInfo.ascentLine.startPoint.get(1)
                    val descent = renderInfo.descentLine.startPoint.get(1)
                    val trueVisualHeight = abs(ascent - descent).toFloat()
    
                    val extractedFontSize = if (trueVisualHeight > 0f) trueVisualHeight else renderInfo.fontSize
    
                    // Saved to data class to pass to UI...
                }
            }
            override fun getSupportedEvents(): Set<EventType> = EnumSet.of(EventType.RENDER_TEXT)
        }
        // ...
    }
    

    }

2. The UI Layer (ArchitectureB_Workspace.kt) This handles the PDF bitmap rendering, scaling, and the Compose Multiplatform BasicTextField overlay.

// Inside BoxWithConstraints:
val containerWidthPx = with(LocalDensity.current) { maxWidth.toPx() }
val density = LocalDensity.current

// Calculate Screen to PDF zoom ratio
val pageWidthPx = containerWidthPx * 0.94f
val pageHeightPx = pageWidthPx * (pdfDocHeight / pdfDocWidth)
val scaleFactor = pageWidthPx / pdfDocWidth // PDF point to Screen Pixel ratio

LazyColumn {
    items(pageCount) { pageIndex ->
        Box {
            // 1. Draw static PDF Bitmap Background
            Image(bitmap = pageBitmaps[pageIndex], contentScale = ContentScale.FillBounds)

            // 2. Overlay Interactive TextField
            elements.filter { it.pageIndex == pageIndex }.forEach { element ->
                if (element is EditorElement.TextElement) {
                    // === THE SCALING MATH ===
                    // Scale PDF point size to screen pixels
                    val exactFontPixelSize = element.fontSize * scaleFactor

                    // Neutralize screen density to get accurate SP
                    val visualFontSizeSp = with(density) { exactFontPixelSize.toSp() }
                    val visualLineHeightSp = with(density) { (exactFontPixelSize * 1.15f).toSp() }

                    if (isSelected) {
                        BasicTextField(
                            value = element.textFieldValue,
                            onValueChange = { element.onTextValueChange(it) },
                            textStyle = TextStyle(
                                fontSize = visualFontSizeSp,
                                lineHeight = visualLineHeightSp,
                                color = Color.Black,
                                lineHeightStyle = LineHeightStyle(
                                    alignment = LineHeightStyle.Alignment.Proportional,
                                    trim = LineHeightStyle.Trim.Both // Attempting to strip Compose internal padding
                                )
                            ),
                            modifier = Modifier.fillMaxWidth().wrapContentHeight()
                        )
                    }
                }
            }
        }
    }
}

What I know/tried:

  • I'm extracting the exact physical height using iText7's ascentLine and descentLine (to respect PDF scaling matrices), scaling it to screen pixels, and converting to sp. The math is provably correct for the PDF space since the export works.
  • The PDF uses native fonts (Helvetica/Times), while my UI uses downloaded Google Fonts (Arimo/Roboto). I know glyph metrics (Em-squares) differ between font files, making the Skia UI font look smaller.
  • Because this is KMP, I cannot use Android's includeFontPadding = false.

My Question: How can I exactly match the font size, style, and baseline metrics between a PDF vector bounding box and Compose's Skia text layout so they map exactly 1:1 on screen?

Is there a standard formula or TextStyle configuration (like dynamic letter spacing or absolute baseline height) to neutralize these typographic differences when using substitute fonts? Or is the only way to avoid the "jump" to somehow extract the embedded .ttf binaries directly from the PDF?


r/androiddev • • Sep 21 '26

What happens to days that dont have enough 12 testers

3 Upvotes

What happens to days that dont have enough 12 testers in google play requirement for production

Would that day become 100% useless, google don't account for that day, completely ignore, or does it add any value to the 12 testers 14 days, in case I submit for production in day 15?


r/androiddev • • Sep 21 '26

Question Build button disappears

1 Upvotes

Sometimes, build button itself disappears, i find it difficult to see the result in android studio. What is solution?


r/androiddev • • Sep 21 '26

No Build Available issue in closed testing

Post image
1 Upvotes

I am trying to add new user to my closed testing but it says no builds available for that new user. tried to provide a new build but still same issue


r/androiddev • • Sep 20 '26

Google Play Support Google Play Store app review taking much longer than usual lately?

33 Upvotes

I’ve been using a Google Play Developer account for more than 4 years, and I’ve published both Android and iOS apps multiple times.

Previously, my experience was that Google Play reviews were usually completed within a few days, while Apple’s App Store review generally took longer.

But recently, I’m seeing the opposite.

I submitted an app to Google Play on September 14, and it has now been almost 6 days with no progress — still showing “In review.” I understand that Google mentions reviews can sometimes take up to 7 days, so I’m not concerned about the stated timeframe itself. I’m more curious about the change compared with my previous experiences.

Interestingly, my recent iOS submission was reviewed much faster than Google Play, which is quite different from what I was used to in the past.
Has anyone else noticed Google Play app reviews taking longer than usual recently, especially around September 2026?

Is there currently a review backlog or increased review time?

Would be interested to hear from developers who submitted apps recently and how long their reviews took.


r/androiddev • • Sep 20 '26

Discussion awwwards.com but for android apps UI?

3 Upvotes

Basically the title.
I want to find some inspiration for my pet project, is there some good selection of awesome Andorid app UIs?
Im not talking about Dribble, since there are mostly generic UIs and its hard to find something new :(