Documentation Index
Fetch the complete documentation index at: https://help.1nspect.app/llms.txt
Use this file to discover all available pages before exploring further.
Mobile Troubleshooting
Mobile-specific issues — sign-in, capture, AI, and device-level concerns. For shared mobile + web issues, see Common Issues & Troubleshooting. For sync-specific issues, see Sync & Offline Issues.Sign-in problems
”This account is not yet active”
Symptom: You sign in with correct credentials but see “This account is not yet active. Please contact your company administrator for access.” Cause: Firebase Auth accepted your credentials, but your tenant access has not been provisioned inuser_registry.
Fix:
- Contact your company administrator
- Ask them to verify your account is provisioned in the web admin
- After they confirm, sign out and back in on mobile
”Incorrect email or password”
Causes & fixes:- Wrong password — tap Forgot password? to reset
- Wrong email — the field is case-insensitive but watch for typos in domain (
gnail.comvsgmail.com) - Account on a different tenant — confirm with admin which email address is registered
- Caps Lock — verify keyboard state
”Too many failed attempts”
Cause: Firebase rate-limited your account for security. Fix: Wait 5–15 minutes. Use Forgot password? to reset if you’ve truly forgotten.”Network error. Check your connection and try again.”
Cause: Device can’t reach Firebase Auth. Fix:- Verify you have signal (Wi-Fi or cellular)
- Try a different network (some carriers block Firebase Auth ports — rare)
- Toggle airplane mode off/on
- Try again
Camera & media problems
”Permission needed — Sorry, we need camera permissions”
Fix:- iOS: Settings → 1nspecT → Camera → toggle ON
- Android: Settings → Apps → 1nspecT → Permissions → Camera → Allow
”Permission needed — Sorry, we need camera roll permissions”
Same fix path but for Photos / Media library:- iOS: Settings → 1nspecT → Photos → All Photos (or Selected Photos)
- Android: Settings → Apps → 1nspecT → Permissions → Photos and Videos → Allow
Photos look low-resolution in the report
Cause: All photos taken via the 📷 button are downscaled to ~1024 px at 0.7 JPEG quality. Fix when you need high resolution: Use 📁 Library Import instead of taking with the in-app camera. Imported photos keep their original resolution.Video won’t upload — fails silently
Cause: Video file is over the platform size limit. Fix:- Recapture a shorter video (< 30 seconds is reliable)
- If you must keep the long version, use the device’s photo app to record + import via 📁 — the platform handles imports slightly differently
Inspection problems
Section / Subsection missing from the Capture Screen nav
Causes & fixes:- Template not Published — operator goes to Template Builder, toggles Published ON
- Old template snapshot — your inspection captured the template at creation time. New sections in the template don’t appear in already-started inspections. Start a new inspection if you need the new section
- Subsection marked inactive — operator verifies the subsection’s Active toggle is on
- App cache stale — force-close the app and reopen
Inspection won’t start — “Start Inspection” button is disabled
Cause: Gating prevents start until prerequisites are met. The disabled button label tells you why:| Label | Meaning |
|---|---|
| Setup Required | Template AND narrative collection not yet assigned. Contact operator. |
| Contract Not Signed | The contract was sent but client hasn’t signed. Wait for client or have operator follow up. |
| (none — fully enabled) | Tap to start |
”Inspection in progress” prompt when starting a new one
Cause: You have an unfinished inspection on the device. The app prompts:Current Inspection in Progress You have an inspection in progress. What would you like to do? [Continue Current] [Start New Anyway] [Cancel]Fix: Continue Current to finish the open one, or Start New Anyway to save the in-progress one and switch.
Findings not saving — “Database not initialized”
Symptom: When tapping Save + New, you see: “Database not initialized. Your deficiency is still on screen — please try again.” Cause: Local storage init race condition (rare). Fix:- Tap Save + New again — usually succeeds on retry
- If the alert persists, the finding is still safely in memory; capture a screenshot, then force-close and reopen the app
- The finding may need to be re-entered
Rating not sticking on a subsection
Cause: Your inspection record has bothI and D set, and the UI is showing one as primary.
Fix: TREC explicitly permits both — see Capture Screen. The UI is showing both correctly; the dual-rating is by design.
AI problems
”Insufficient IT Tokens”
Symptom: Tapping an AI button shows: “Insufficient IT Tokens. Vision Analysis requires 8 IT. Purchase a top-up pack in Settings.” Cause: Tenant’s IT balance is too low for the operation. Fix:- Have your administrator top up in the web admin → Settings → Subscription & Tokens
- In the meantime, continue inspecting without AI (template fallback narratives work fine)
”Photo Required” when running Vision Analysis
Cause: Vision toggled ON but no photo captured. Fix: Capture a photo first, then tap ✦ AI Generate. Or turn the 👁 Vision toggle off to use text-only generation.AI Generate returns generic / wrong narrative
Causes & fixes:- Caption too vague — write a more specific caption (6–15 words mentioning the component, the condition, and the location)
- Wrong section/subsection selected — the AI uses section context. Re-select and regenerate
- Template’s inspection standard is wrong — verify in template settings; should be
TRECfor Texas residential
”⚠️ AI Offline — A template CAR narrative has been pre-filled”
Cause: AI service is unreachable. Fix: None needed — the template narrative is pre-filled and editable. No IT cost was deducted. AI will work again once the service returns.Co-Inspector findings keep appearing for the same issue
Cause: Co-Inspector targets >85% confidence findings; sometimes it flags the same area across photos. Fix:- Use ✕ Skip on duplicates
- If a finding genuinely is the same as the primary, edit the caption to indicate (e.g. “Same issue, different angle”)
App behavior
App crashes on launch
Causes & fixes:- Corrupted local data — uninstall and reinstall. (You may lose un-synced local-only data — verify all inspections show as synced in Review tab before doing this)
- Old version — open the App Store / Play Store, update to latest
- iOS / Android version too old — 1nspecT supports iOS 15+, Android 9+
Splash screen (“1nspect” + spinner) stuck
Cause: Firebase Auth resolution is hanging. Fix:- Wait 30 seconds; sometimes networks are slow
- Force-close (swipe app away on iOS, recent apps menu on Android) and reopen
- If persistent, check network — Firebase Auth requires a working internet connection on launch
Tabs not responding / app feels frozen
Fix:- Force-close and reopen
- If still unresponsive, restart the device
- If persistent after restart, uninstall and reinstall
”Application Error” red screen
Cause: A React Native error boundary caught an unhandled error. Fix:- Scroll down to read the error message and stack trace
- Screenshot the error
- Email support@mymavtech.com (use the Contact Support action if accessible) with the screenshot and what you were doing
Performance issues
App is slow when scrolling Review tab
Cause: Inspections with 100+ findings can lag on older devices. Fix:- Use the section filter in Review to load fewer findings at a time
- Mark complete and finalize — the Inspection Reviewer on web handles large inspections better
Photo gallery hangs when opening 📁
Cause: Device library has thousands of photos; library access is slow. Fix:- Limit the app’s Photos permission to “Selected Photos” — only the photos you’ve explicitly granted are scanned
- iOS: Settings → 1nspecT → Photos → Selected Photos
Related articles
- Common Issues & Troubleshooting — shared mobile + web issues
- Sync & Offline Issues — anything to do with cloud sync
- Mobile App Overview
- Settings & Tokens — Contact Support action