Whilst trying to push an AR scene (that works on iOS) to an Android device I get the following error message
"Assets/Qualcomm Augmented Reality/Scripts/CylinderTargetBehaviour.cs(97,26): error CS0115: `CylinderTargetBehaviour.OnFrameIndexUpdate(int)' is marked as an override but no suitable method found to override"
Any help would be great, thank you
Ok I've did like you told me.
Downloaded cylindertargets-2-6-7.unitypackage from https://developer.vuforia.com/resources/sample-apps/cylinder-targets?t=unity-4813791
and built it. Worked perfectly without any problem. Unfortunately I got the same error again on another project, but i was able to make a very dirty "fix". I just deleted all the Cylinder*** Scripts and the KeepAlive Script. Of course I am not using the cylindertargets in my projects right now. The error doesn't seem to be reproducable to me either, as it seems to just randomly pop up while developing. If you want to contact me just write me an e-mail. I can't hand out my projects as they have client related contents.
kind regards
GrannySmith
Any update on this ?
We tried to reproduce this issue but we were unable to do so; I suspect that the issue might be related to some mis-configuration or incorrect installation of the Java or Android SDK on your system,
or (second hypothesis) that this could be due to an incorrect migration issue.
Is any of you migrating from a previous version of the SDK ?
Hi GrannySmith,
could you try the following procedure:
- create a fresh new unity project
- import the CylinderTargets sample package (just that and nothing else)
- try to build and run the sample
This would be really helpful to understand if the issue is related to the asset import process (or something else).
Your help much appreciated..
Just wanted to say, that I've got the same problem. I think that I got it after reimporting the Vuforia unitypackage, but to be honest I am not quite sure.
EDIT: I tried to "repair" the project by deleting the Qualcomm Files manually and importing them again. Now I get some more errors
Thanks for sharing this feedback. As it seems to popup a bit randomly (i.e. under unclear circumstances), and seems it is not reproducible on the sample, we will keep monitoring this issue.
If you (or others in this thread) in the future have any additional information that can shed some more light on the issue reproducibility, feel free to share.