Troubleshooting

This means the app shipped from a development build that's looking for a Metro bundler. If you got this from the Play Store, force-stop the app, clear cache (Settings > Apps > ShotKit > Storage > Clear cache), and reopen.

If you got this from a side-loaded APK, you have a debug build - you'll need a release build (.aab) for normal use.

Still broken? Email us with a screenshot and the build version (Settings > Apps > ShotKit > Version).

Usually a network or cache problem. Try in order:

1. Confirm the device has internet (open any web page).
2. Force-stop ShotKit and reopen.
3. Settings > Apps > ShotKit > Storage > Clear cache (NOT Clear data - that wipes saved missions).
4. Restart the device.

Usually a Google Play Services issue on the device. Update Google Play Services from the Play Store, restart the device, then try again. ShotKit needs a recent Play Services for Maps and Location.

Still broken? Email us with your device model + Android version.

The Google Maps tile server isn't reachable. Most often a network issue (firewall, captive portal, or VPN that blocks Google). On corporate or school Wi-Fi, switch to mobile data and reload the app.

If the map is grey only in 3D mode but works in 2D, check the FAQ entry on offline use - 3D Earth always needs a live connection for tiles.

Three things to check:

• Permission. Settings > Apps > ShotKit > Permissions > Location must be Allowed (Precise, not Approximate).
• OS-level location. Quick Settings - the Location toggle must be on.
• Indoor vs outdoor. GPS needs a sky view. If you're inside, the device may take 30-60s to get a fix or fall back to network triangulation (less accurate).

If GPS is denied, you can still set the launch site by tapping the map directly or searching for an address.

The search uses Google Places. If a venue is too small to be indexed, try:

• The nearest town or landmark instead, then drag the pin to the exact spot.
• Latitude, longitude typed directly (e.g. -29.5042, 28.9845).
• The map's tap-to-set mode - tap anywhere on the map to drop a pin.

Fixed in v171 (May 2026). If you still see this on the latest build, force-close and reopen so the app picks up the new asset cache, then try again. If it still happens, email us with steps to repro - the camera-state-sync code path is one we watch closely.

Also fixed in v171. Same instructions as above - force-close to clear the WebView cache, reopen, retry.

Three required inputs - all must be set before generation is enabled:

1. A drone selected in the top header dropdown.
2. A subject location pinned on the map.
3. A non-empty Shot Description.

If all three look set but the button is still off, scroll the sidebar - sometimes a hidden validation message is below the fold.

The AI service is rate-limited per account during testing. Wait 30 seconds and retry. If you keep hitting this in a short window, you may have hit the daily quota - it resets at 00:00 UTC.

ShotKit uses SRTM elevation data which is accurate to ~30m horizontal resolution - good enough for terrain but not for individual structures. After generation:

1. Inspect the altitude chart on the result card. Any waypoint dipping into the grey "ground" band is unsafe.
2. Tap Auto-raise terrain on the result card - it bumps clipping waypoints to a safe vertical buffer.
3. For city flights, manually inspect the path for buildings the SRTM doesn't model. Drag waypoints up if needed.

Always do a low-altitude reconnaissance pass before running a planned mission at full speed.

The AI maps your prompt to a template - sometimes it picks the wrong one when the description is ambiguous. Tips:

• Be explicit about geometry. "Orbit at 60m" beats "circle around it".
• State the duration. "90 seconds long" or "8 minutes total".
• Mention the camera direction. "Facing the building" vs "facing outward".
• Use Inspire me (sidebar) for AI shot suggestions worded the way the model expects.

Use the Remix button on the result card to refine - "same orbit but slower" / "same path but at 80m" / "same shot but counterclockwise".

DJI Fly is picky about file paths. Most common cause: the KMZ was downloaded into the device's Downloads folder, which DJI Fly can't see directly. Move it to DJI/waypoint on your device storage (or onto the drone's SD card in the same folder), then DJI Fly will pick it up on next launch.

If the file is in the right place but still rejected, check that you haven't renamed it - the .kmz extension is required (not .kml or .zip).

Pilot 2 sometimes silently fails to parse a mission with too many waypoints (its hard limit is around 200). If your generated mission exceeds this:

1. Open the mission in ShotKit and lower the waypoint density (the result card has a "Simplify" option).
2. Or use the Sequences feature to split a long shoot into multiple back-to-back missions.

This is DJI's geofence, not ShotKit. The launch zone or some part of the planned path overlaps a DJI restricted area. Two options:

• Apply for a flight unlock through DJI FlySafe if you have legitimate authorisation.
• Re-plan the mission to avoid the restricted zone. The Airspace overlay in ShotKit highlights known zones to dodge.

ShotKit accepts standard DJI WPML KMZ. KMZ files from Litchi, DroneDeploy, or other planners use different schemas and won't import directly. Convert via DJI Fly's import-then-re-export flow if you must, or recreate the mission natively in ShotKit using the Draw Route or template options.

Common culprits:

• Battery saver / low power mode - throttles GPU. Disable when planning.
• 3D Earth view is heavier than 2D. Drop back to 2D for raw performance.
• Lots of waypoints (200+) on screen. Toggle waypoint visibility off in the result card if you just need the camera-path overview.
• Older Android tablets with WebView versions older than 110. Update Android System WebView from the Play Store.

The sun calculator uses your device's local time and the subject's coordinates. If something is off:

• Confirm the device's time zone matches your physical location (Settings > System > Date & time > Use network-provided time zone).
• The time slider in the Flight Planning section lets you preview any moment - use it to confirm sunrise / sunset are roughly when you'd expect.

The marker matches the drone you've selected in the header dropdown. Switch drones and the marker updates on the next render. If a specific model is missing or its image is generic, email us - we add new drone artwork as more models go through testing.

ShotKit locks an account for 15 minutes after 5 wrong-password attempts in a row. The clock resets on each successful login. If you've forgotten your password, use the "Forgot password" link below the sign-in form to receive a reset email - this clears the lockout.

1. Check spam / promotions folders (the sender is noreply@shotkit.stewartb.workers.dev).
2. Confirm you typed the same email address you signed up with - typos in the reset form silently succeed but no mail arrives because no account matches.
3. Wait 5 minutes. SMTP can lag.
4. If still missing, email us from the address that's on the account.

Mission history is tied to your account, not the device. Sign in on the new device with the same email + password and your missions, saved locations, and prompt history all reappear. If they don't, email us with the email address - we can manually re-link.

Not yet supported. Email + password only for the current testing window. If you have a strong organisational requirement (corporate Google Workspace, etc.), tell us - it helps us prioritise.