FAQ & Troubleshooting

Common problems and simple fixes

A beginner-friendly troubleshooting page for Oviora Builder, Windows Installer, Android SDK, ADB, Gradle, Firebase and native Android feature tests.

oviora command not found

Open a new PowerShell window after installation and run:

where.exe oviora

Expected first result:

C:\Oviora\portable-bin\oviora.cmd

If not found, reinstall Oviora Builder or check User PATH for C:\Oviora\portable-bin.

Wrong oviora command is running

If where.exe oviora shows an old NPM command before the portable command, the portable path must be placed first.

C:\Oviora\portable-bin\oviora.cmd

oviora.config.json not found

Cause: you are not inside an Oviora project folder.

cd YourAppFolder
oviora br

Android SDK path not found

Run:

oviora doctor

Check ANDROID_HOME, ANDROID_SDK_ROOT, platform-tools and cmdline-tools.

No Android device found

adb devices
  • Enable Developer Options
  • Enable USB Debugging
  • Reconnect USB cable
  • Accept the phone permission popup
  • Use a data-transfer USB cable

APK install failed

Possible causes: phone not connected, USB debugging not allowed, old app conflict, version downgrade, or low storage.

adb devices
adb uninstall your.package.name
oviora br

Version downgrade error

INSTALL_FAILED_VERSION_DOWNGRADE

Fix option 1:

adb uninstall your.package.name
oviora br

Fix option 2: increase versionCode in app/build.gradle.

Java compile error

Check oviora/java/MainActivity.java.

  • Missing import
  • Wrong package line
  • Wrong variable name
  • Wrong XML id
  • findViewById points to missing id

Android resource error

Check:

oviora/layout/
oviora/images/
oviora/values/

Common causes: invalid XML syntax, missing drawable, wrong @drawable/name, wrong @color/name.

default_web_client_id not found

Possible causes: Google services Gradle plugin not applied, google-services.json not copied, or Firebase package mismatch.

oviora sync
oviora br

Also check build.gradle, app/build.gradle, and app/google-services.json.

Google Sign-In error code 10

Usually caused by SHA-1 mismatch.

.\gradlew.bat signingReport

Add SHA-1 in Firebase Console and download a fresh google-services.json.

Native feature tests

  • Notification: Android 13+ needs POST_NOTIFICATIONS permission.
  • Camera: camera permission must be allowed and a camera app must exist.
  • Microphone: microphone permission must be allowed.
  • Location: GPS/location must be ON and permission allowed.

Security Notes for Developers

Never upload these private files to GitHub or public examples:

serviceAccountKey.json
firebase-adminsdk.json
private_key
.env
*.jks
*.keystore
signing.properties

For public demo repositories, prefer google-services.sample.json. Do not paste private keys into README files, issues, commits, screenshots or public videos.