Troubleshooting

Troubleshoot: loading, restarts, black screens and pop-ups

Distinguish normal game loading from a stalled foreground, unnecessary restart or blocking promotion and dialogue.

A brief black screen can be normal#

Viking Rise and the Android emulator can show a short black or transitional screen while the activity remains foregrounded. The automation should allow a bounded loading period and look for a recognisable screen before deciding the game is unavailable.

Repeated restarts are not normal if the game was continuing to make progress. Capture the approximate timing, whether the app process changed and the final visible screen.

Blocking UI#

Promotions and purchase offers

Close through a visible dismissal control. Do not interact with purchase buttons.

Story or decree dialogue

Advance or dismiss only when the dialogue is recognised and the action is clearly non-destructive.

Reward animations

Allow the animation and resulting state to settle before continuing.

Exit confirmation

Cancel an unintended exit prompt; do not confirm game closure during a routine.

Unknown screen

Stop for inspection rather than tapping blank space repeatedly.

Recovery steps#

  1. 1

    Stop the active routine

    Prevent further input while the current state is unclear.

  2. 2

    Wait briefly

    Confirm whether the loading or animation resolves naturally.

  3. 3

    Dismiss only recognised blockers

    Use the visible close or continue control.

  4. 4

    Return to a normal city or map state

    Then rerun only the affected workflow if its previous side effect is known.

Keep the sequence, not just the final black screenshot#

Record when the game started, when the screen last changed and whether the emulator still responds. Capture the first unexpected screen and a later observation. A moving loading indicator, a download prompt and a frozen blank frame are different evidence.

If the game works manually with automation stopped, retain that comparison for support. If it does not, investigate the game or emulator first. Do not extend every timeout or repeatedly restart the fleet to hide one unresolved loading condition.

Still stuck?

Complete the evidence checklist before contacting support. Never send passwords, recovery codes, payment details or private licence material.

Prepare your report

DIAGNOSE BEFORE RETRYING

Review the state before another attempt.

Keep the first unexpected observation and check what may already have happened. Understand the verification approach, then prepare a focused support report if the result remains unclear.