First launch failed: when to use the contact form instead of uninstalling
An app that installs but does not open is one of the most common tickets in the support inbox. The right move is rarely to uninstall.
The wrong move
If you tap the Yono VIP Game icon and the app immediately closes, the first instinct is to uninstall and reinstall. That usually destroys the cache and any local logs the support team needs to diagnose the failure.
The right move
Open the contact form at /contact/. Choose "Install or first launch" as the topic. Include the device model, Android version, the brand of the Yono VIP Game build you installed, and a screenshot of the crash if your phone shows one.
What the support team does next
The support team reads the ticket, checks the latest known issues for your device model, and replies through the same form. Common replies are: clear the cache (not data), update the system webview, or wait for a fix in the next package version.
When to clear data instead
If the support team cannot resolve the crash and the app is unusable, the team will reply with permission to clear data. Only clear data after that permission is granted. Clearing data removes your local account settings, so the team will warn you before you do.
What the support team does not do
The support team does not ask for your password, OTP or full account number. If a message claiming to be from the support team asks for those details, close the message and report it through the contact form.
Related reading
Read install safety and unknown sources explained for the matching preflight and prompt background.
Open the contact form and start the diagnosis
Tickets are tracked server-side and replies use the same form.
If the app opens to a blank screen or crashes before login, send the device model through /contact/ before clearing data.
Editorial frame
Editorial frame for the contact support first launch hub.
Why not to clear data first
Clearing data resets the partial install state on some Android skins. Once data is cleared, the support team can no longer trace the failure mode against the staged record. The ticket becomes a guess instead of a confirmation.
Send the device model, Android version, and a screenshot of the crash dialog through /contact/ first. The support inbox will reply with either a known fix or a request to clear data only if the trace confirms it is safe.
Clearing data also resets any local cache that the support team could have used to identify the failure. The ticket is harder to resolve without that cache.
What the support inbox can do
Match the crash dialog text against the staged record. If the text matches a known fix, the reply includes the fix; if it does not, the reply asks for the device model and Android version to refine the search.
Open a server-side trace for first-launch failures. The trace confirms whether the package was installed cleanly and whether the destination surface received the install ping.
Escalate the trace to the destination surface team if the local failure cannot be reproduced. The destination surface team has access to crash logs that the local support team does not.
What to include in the ticket
Device model - for example Pixel 7, Samsung Galaxy A54, Redmi Note 12.
Android version - Settings → About phone → Android version. The full version string is more useful than just the release number.
Screenshot of the crash dialog. The text below the crash icon is the part that matches against the staged record.
Source URL - where you came from before tapping Install App. This helps the support inbox confirm the package source.
Common first-launch failures
Crash on splash screen - the package was installed but the destination surface failed to load. The fix is usually a clear cache and retry.
Crash on sign-in screen - the destination surface failed to authenticate the phone number. The fix is usually a network reconnect.
Blank screen after splash - the destination surface loaded but the rendering pipeline failed. The fix is usually a phone restart.
Stuck on verifying - the destination surface failed to verify the install. The fix is usually a clear data and retry.
Crash on profile area - the destination surface failed to load the user's profile. The fix is usually a sign-out and sign-in.
What the support inbox can do
Match the crash dialog text against the staged record. If the text matches a known fix, the reply includes the fix.
Open a server-side trace for first-launch failures. The trace confirms whether the package was installed cleanly.
Escalate the trace to the destination surface team if the local failure cannot be reproduced.
Reply with a workaround if a fix is not yet available. The workaround usually involves a clear cache or a sign-out.
Track the failure across multiple reports. If the same failure is reported by multiple users, the destination surface team prioritises a fix.
Common first-launch failures and their fixes
Crash on splash screen - clear cache and retry.
Crash on sign-in screen - reconnect to the network and retry.
Blank screen after splash - restart the phone and retry.
Stuck on verifying - clear data and retry from step 1.
Crash on profile area - sign out and sign in.
What to do if the fix does not work
Send the device model, Android version, and a screenshot of the failure to /contact/.
Open a server-side trace. The trace confirms whether the package was installed cleanly.
Escalate to the destination surface team if the local failure cannot be reproduced.
Reference list
Tickets that include the device model, Android version, and a screenshot are typically resolved faster than tickets without those details.
Tickets that include the package name and the source URL are typically resolved faster.
Server-side traces confirm whether the package was installed cleanly and whether the destination surface received the install ping.
Cross-team coordination tickets typically resolve within five business days with an interim reply.
Reference comparison table
Tickets that include the device model, Android version, and a screenshot are typically resolved faster.
Tickets that include the package name and the source URL are typically resolved faster.
Server-side traces confirm whether the package was installed cleanly.
Cross-team coordination tickets typically resolve within five business days with an interim reply.
The support inbox does not store the email address beyond the ticket lifecycle.
Clearing data resets the partial install state on some Android skins.
Closing reference
Clearing data resets the partial install state on some Android skins. Once data is cleared, the support team can no longer trace the failure mode.
Send the device model, Android version, and a screenshot of the failure to /contact/ first. The support inbox will reply with either a known fix or a request to clear data only if the trace confirms it is safe.
Tickets that include the device model, Android version, and a screenshot are typically resolved faster than tickets without those details.
Cross-team coordination tickets typically resolve within five business days with an interim reply.
Editorial closer
Clearing data resets the partial install state on some Android skins. Once data is cleared, the support team can no longer trace the failure mode.
Send the device model, Android version, and a screenshot of the failure to /contact/ first.
Tickets that include the device model, Android version, and a screenshot are typically resolved faster.
Cross-team coordination tickets typically resolve within five business days with an interim reply.
The support inbox does not store the email address beyond the ticket lifecycle.
Detailed readme on the contact support article
If the app opens to a blank screen or crashes before login, send the device model through /contact/ before clearing data.
Clearing data resets the partial install state on some Android skins. Once data is cleared, the support team can no longer trace the failure mode.
Tickets that include the device model, Android version, and a screenshot are typically resolved faster than tickets without those details.
Cross-team coordination tickets typically resolve within five business days with an interim reply.
The support inbox does not store the email address beyond the ticket lifecycle.
Editorial cadence note
Clearing data resets the partial install state on some Android skins. Once data is cleared, the support team can no longer trace the failure mode.
Tickets that include the device model, Android version, and a screenshot are typically resolved faster.
Cross-team coordination tickets typically resolve within five business days with an interim reply.
Editorial closer
Server-side traces confirm whether the package was installed cleanly and whether the destination surface received the install ping.
Cross-team coordination tickets typically resolve within five business days with an interim reply.
The support inbox does not store the email address beyond the ticket lifecycle.
Closing line
The support inbox replies within one business day for install and first-launch issues.
Account access tickets that require identity verification can take up to three business days.