VR app with errors

Welcome! Forums Unity Plugins Mobile Speech Recognizer VR app with errors

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
  • #1241

    I have built an app using Google Cardboard.
    But is coming up with the following errors.

    Before you click on the button it says
    “Cannot use Speech Recognition, Authorization status id Denied”

    But when I click on the button.
    “Something went wrong…Tryagain!
    [[9] insufficient permissions, check your manifest file]

    I have added the two lines to the manifest file as per the instruction.

    and if I make a fresh unity file and run your example on my Samsung note 8, it works fine.

    Is there some where I am missing for this to work?



    Are you using runtime permissions introduced in Android 6.0?

    If so this part might be helpful for you:

    untime permissions in Android 6.0 (Marshmallow)
    If your app is running on a device with Android 6.0 (Marshmallow) or later and also targets Android API level 23 or higher, your app uses the Android Runtime Permission System.

    The Android Runtime Permission System asks the app’s user to grant permissions while the app is running, instead of when the app is first installed. App users can usually grant or deny each permission when the app needs them while the app is running (for example, requesting camera permission before taking a picture). This allows an app to run with limited functionality without permissions.

    Unity does not support the Runtime Permission System, so your app prompts the user to allow what Android calls “dangerous” permissions on startup. See Android’s documentation on dangerous permissions for more information.

    Prompting your user to allow dangerous permissions is the only way to ensure plug-ins don’t cause crashes when they are missing a permission. However, if you don’t want your Unity Android app to ask for permissions on startup, you can add the following to your Manifest in either the Application or Activity sections.

    Adding this completely suppresses the permission dialog shown on startup, but you must handle runtime permissions carefully to avoid crashes. This method is only recommended for advanced Android app developers.

    For further information about the Runtime Permission System and handling permissions, see the Requesting Permissions section of the Android Developer documentation.


    Thanks for the info.
    I got it working. It was something as simple as going into Settings/Apps and turning on the permission for the microphone.

    That’s what happens when you fault find at midnight!

Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.