mcbublick Posted June 8, 2023 Share Posted June 8, 2023 Link to comment Share on other sites More sharing options...
Alex_HTC Posted June 8, 2023 Share Posted June 8, 2023 Make sure that the android package name hasn't changed and also that there are elements fro the controller and minwave version <application> section (\n to separate lines) <meta-data android:name="com.htc.vr.content.NumDoFHmd" android:value="6DoF"/> \n <meta-data android:name="com.htc.vr.content.NumDoFController" android:value="6DoF"/> \n <meta-data android:name="com.htc.vr.content.NumController" android:value="2"/> \n <meta-data android:name="minWaveSDKVersion" android:value="1" /> as specified here Link to comment Share on other sites More sharing options...
mcbublick Posted June 8, 2023 Author Share Posted June 8, 2023 9 minutes ago, Alex_HTC said: Make sure that the android package name hasn't changed and also that there are elements fro the controller and minwave version <application> section (\n to separate lines) <meta-data android:name="com.htc.vr.content.NumDoFHmd" android:value="6DoF"/> \n <meta-data android:name="com.htc.vr.content.NumDoFController" android:value="6DoF"/> \n <meta-data android:name="com.htc.vr.content.NumController" android:value="2"/> \n <meta-data android:name="minWaveSDKVersion" android:value="1" /> as specified here thanks for the swift reply ! we will try this ! btw , we could not see it originally in docs https://developer.viveport.com/documents/sdk-wave/en/VRActivity.html Link to comment Share on other sites More sharing options...
Alex_HTC Posted June 8, 2023 Share Posted June 8, 2023 @mcbublick Oh, right and you need to make sure to increment the android build number as well and signed with the same key that you used originally (not the debug key!) Link to comment Share on other sites More sharing options...
Vector B Posted June 9, 2023 Share Posted June 9, 2023 Thank you, you really helped ! We forgot to sign the app. Was simply that. We were running on debug key. 😅 I was focusing my effort on the android manifest as the error message says, thinking there was something wrong with it. (Signing the app has something to do with android manifest ? I'm not an android dev) You could probably add "Make sure app is signed" in the error message, even if this sounds obvious. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now