Posting this because I lost a stupid amount of time on it and I doubt I'm the only one.

App just closes on Android. No red screen, nothing in Metro, DevTools disconnects. I did what everyone does: rerun, clear cache, paste the code into AI a few times.

The reason was in logcat the whole time. Native code threw, the app died before JS could say anything, and the Android log had the exact line.

What worked for me:

- open the android folder in Android Studio and open Logcat (it picks up the app even if you started it with yarn run android)

- clear it, then reproduce the crash

- set the level to Error and search FATAL EXCEPTION

- read the exception message first, then the first line in the stack trace that isn't Handler / Looper / ActivityThread. Click it and it jumps to the code

One thing that got me: in the terminal, filtering by pid after a crash gives you nothing because the process is gone. adb logcat -d -s AndroidRuntime worked better.

Also the stack trace only told me where it died, not who passed the bad value. I needed a breakpoint for that part.

I made a small demo crash and recorded the whole thing for anyone who'd rather watch than read: https://youtu.be/oVYBmnOVaI8

What do you check first when Metro says nothing?

https://github.com/M5Devs/VPortable

For infos

Hi,

Our organization developer account (TosiMarketplace) was terminated under the Play Console Requirements and Developer Distribution Agreement Section 11.4. Our appeal was rejected, and support forms now redirect to ticket 6-7479000041612.

During registration we made two mistakes:

1. The organization name entered in Play Console did not exactly match the legal company name on our D-U-N-S profile.
2. The $25 registration fee was paid with the founder's personal credit card, because the company card had not yet been issued.

We suspect these mismatches caused the account information to be treated as inaccurate under Section 11.4, but we are not certain.

We have our corporate registration documents, matching government-issued IDs, and our D-U-N-S profile available.

Our questions:

1. Do these mismatches explain the termination, or should we look at something else?
2. Is there any way to request a human review to correct these details after an appeal has been rejected?

Thank you.

Couple of days ago I made a fresh Google account using Firefox developers browser and my phone number (which has another 2 associated Google accounts), after making the account I signed out, next day I signed in again went to developer section, meanwhile I was informed that I have to make a website that will describe the developer and provide the text of privacy policy and terms of service.

So I went directly to github and tried many times to sign up using Google and each time the OAuth took me again to the sign in page in github, so I decided to try from another device (same wifi) and another browser, this time everything went smooth and I opened my session on github and started my website, meanwhile google started the "verify it is you" scenario and started the robot tests and stuff, finally the send sms gave error of too many attempts try again after several hours!

I leaved it for 2 days to cool down, today when i tried and after making me send sms 2 times it showed a messages that the account was looking like it was created or used with multiple other accounts...etc and it will be considered for deletion after 1 year with an option to submit appeal!

Where did I go wrong and what should I do to avoid such a problem in the future? Need someone with developer background to help me.

I've been building NetPulse, a lightweight Android app for checking your network quality. It has a Material 3 interface with light and dark themes.

What works in v0.1.0-beta:

- Live ICMP ping monitor with Start / Stop

- Latency, min / average / max, jitter and packet loss over the last 300 samples

- Only two permissions (INTERNET and ACCESS_NETWORK_STATE), no ads, no analytics, nothing uploaded

What's coming next: a DNS benchmark (Cloudflare, Google, Quad9, Control D) measured separately from ping, latency charts, test history and CSV export.

The app uses the system ping tool, so some phones may block it. That's the main thing I want to find out: does it work on your device? Please tell me your phone brand and Android version, and any bugs or features you'd like to see.

Beta APK: https://github.com/Mireli5656/NetPulse/releases/tag/v0.1.0-beta

Source code: https://github.com/Mireli5656/NetPulse

The beta is signed with a debug key, so uninstall any earlier NetPulse build before installing it.

Thanks for trying it!

Wanted the iOS 26 liquid glass look in a Compose app, so I made a version and tuned the shaders side by side with a real iPhone. Putting it on GitHub in case anyone else needs it.

It works, but it’s an early version. If anyone wants to contribute to bringing liquid glass over fully, I’d be happy to have you. Issues and PRs welcome.

Hi everyone,

I'm planning to transfer my app from one Google Play Console developer account to another.

For those who have already completed an app transfer, how long did it take for Google to approve and complete the transfer?

Did it take a few days, a week, or longer?

I'd appreciate it if you could share your experience. Thanks!

For those building apps for clients: how do you get access to the client's App Store Connect and Google Play Console at the start of a project? Do they invite you with a role, share a login, or do you publish under your own account and transfer the app later?

1. How long does it usually take until you can upload a build?
   
2. Which part trips clients up most: the developer account itself, D-U-N-S, roles, two-factor?
   
3. When the project ends, how do you hand things back?

Curious what works for you and what doesn't.

Wondering if anyone has faced similar and if there are any common gotchas…

app works fine in simulators, devices via local upload and also happily running in open test via play store.

switch on minify/proguard/etc in both debug and release builds.

all still runs fine EXCEPT when it goes through play store - never gets past internal test - crashes during API call. It smells of GSON deserialisation but the only way I can reproduce it is to push it through the release process.

any ideas about what I am likely missing? all suggestions welcome.

thx.

Hey everyone! I’m curious how other mobile app developers reacted to the Gravy Analytics breach and whether it led you to do anything differently with your own apps. I created a poll below and hope you could take a vote.

If none of those quite fits, feel free to share your take in the comments. If you made changes, I’d love to hear what you changed. And if you considered making changes but ran into obstacles, I’d be interested in hearing about that too. Thanks for sharing!

Background, if you’re unfamiliar: Here’s WIRED’s coverage of the breach and its connection to mobile app location data.

Which option comes closest to your experience?

This continuation to previous post https://www.reddit.com/r/androiddev/s/9m7RVVu6o7

added compose UI support for LED matrix, specifically max7219
also created playground to easily test it on browser without actual hardware

here is video from actual LED matrix hardware

Looks like manually calling Tink to encrypt data is no longer needed

Google Play is adding memory thresholds for Android apps starting February 2027. They're measured using dynamic memory (anonymous RSS + swap) at p90 over 28 days.

I started looking into these thresholds and ended up going through the memory metrics Android gives: Java heap, native heap, RSS, PSS and swap. I break down each metric in this post and explain why Google Play uses dynamic memory instead of the others.

https://measure.sh/blog/android-memory-monitoring

Just a reminder: this doesn't follow any modern standards, as it’s designed for Android 2.0 phones (and before anyone asks why—there are still many communities that use them on a daily basis, and I’m one of them). I’m not posting this to show off; rather, I’m looking for suggestions based on Material Design UI.

I am developing a mobile app, which has a react native frontend, nest.js as the backend and for db and authentication, I'm planning to use supabase.

Now, currently as my app is in its initial stages I'm planning to use the supabase, as it free tier provides ample limits for my use case.

However, in later years if my app grows. I may think of switching to a cheaper alternative.

So, what I am planning to follow is for authentication, route the requests to my backend and inturn the backend will communicate with the supabase to authenticate the user. The backend will save the supabase token, create a separate session token for the user and send it back to the user.

My main reason for doing this is, I want the authentication to be provider independent and any changes needed should be done on the backend instead of the app.

Please let me know, if this approach is correct. What are the pros and cons. How much effort it would require to implement this. Will the security concerns increase if my backend starts handling this instead of the supabase only.

I also want to integrate the google and apple login as well. How will this approach affect it?

Also, if there any other better approaches, please let me know.

Hi everyone! I'm a beginner Android developer building an app using Kotlin and Jetpack Compose.

Currently, my Pro features are free in debug mode. I want to publish my app for closed testing and implement Google Play subscriptions.

My questions:

1. How can I give closed testers free access to all Pro features without requiring payment?

2. Should I use license testers or implement a separate tester-only Pro access mechanism?

3. How can I ensure normal users must pay for a subscription after the production release?

What's the simplest and safest approach? Any guidance would be appreciated. Thanks!

https://play.google.com/apps/internaltest/4699517858335076276

Above is my first app and google needs testing. Could anyone of you download and test?

Hi everyone,

I’m working on an AI application running on a SpacemiT K3 COM260 RISC-V board with a custom-built Android/AOSP environment.

Currently, my application performs AI inference using the general-purpose CPU cores (X100). I want to move the inference workload to the board’s 8 dedicated A100 AI cores to improve performance.

Current setup

Hardware: SpacemiT K3 COM260 RISC-V board

OS: Custom-built Android/AOSP

Inference framework: ONNX Runtime

Access: ADB shell available

Current execution: General-purpose CPU cores

Target: 8 A100 AI cores

Questions

Is there an Android-compatible SpaceMITExecutionProvider or an official SDK/runtime for the K3 A100 AI cores?

If not, what would be the recommended approach to port the existing SpacemiT ONNX Runtime backend to Android/AOSP?

Are the A100 cores exposed as schedulable CPU cores, or must inference be submitted through a separate driver/runtime API?

Can standard ONNX Runtime be configured to use these cores, or is a vendor-specific execution provider and optimized operator library required?

Are there any sample projects, build instructions, kernel configurations, or documentation for running ONNX Runtime inference on A100 under Android?

I’d appreciate advice from anyone who has worked with SpacemiT K3, RISC-V AI acceleration, Android NDK, or custom ONNX Runtime execution providers.

My goal is to keep the existing Android application and ONNX model where possible, while changing the inference execution backend to use the A100 hardware.

Thanks in advance!

Hii, I have an upcoming Google android + dsa interview for L4. I have a few doubts around it:

1. How will the interviewer cover android + dsa in mere 45 ins ?

2. Will the dsa ques be based on android stuff, or will it be pure dsa, basically are android and dsa in this round dependant on each other ?

3. Can I be asked to write code for an android app?

For anyone who has taken this interview, please share your insights on the android + dsa rounds.

Thanks in advance :)

Android Recovery currently uses Minui, which directly manipulates the framebuffer: Minui source code.

This project aims to use Minui as a backend for the Compose Runtime, enabling the development of UIs for Android Recovery, battery charging screens, and other system-level interfaces that operate completely independently of the Android Framework.

The Play Console is flagging my app with the DEX code optimization warning (requiring R8 shrinkage and obfuscation on release builds).

Here's the catch-22: Whenever I enable R8 for a release build, the app runs completely fine locally across my physical and virtual test devices. However, as soon as I submit it to Play Console (even on Closed Testing), the automated review bot rejects it for "Unresponsive app / Broken Functionality."

• Telemetry Gap - Neither Android Vital nor Firebase Crashlytics records any crash or ANR during the review window.
• Support Wall - Support refuses to provide stack traces, logcat dumps, or even clarify which version code failed.

Disabling R8 entirely and resubmitting allowed the app to pass review, proving R8 is triggering something specific on Google's automated test harness.

My app is an edge AI tool with a large local model footprint (2 GB). I suspect the R8 build might be breaking reflection in a background dependency or causing a thread lock or startup delay on their test labs that triggers an ANR.

Questions for the community:

• Has anyone successfully debugged an R8-only rejection when Play Console refuses to provide logs?
• How can I simulate the exact environment Google's automated review bots use during pre-launch?

Edit:
I submitted a feature request to Google's MediaPipe asking for example ProGuard rules, since their example currently lacks the configuration:
https://github.com/google-ai-edge/gallery/issues/1408