Log in or register to post comments

Best practice for both Android and iOS in single project

March 16, 2012 - 12:10pm #1

Should I import the Vuforia Android first or the Vuforia iOS first, assuming I would like to keep a single project for export to both iOS and Android

Are there any other caveats to be aware of when trying to use one project for multiple platforms?

Best practice for both Android and iOS in single project

July 30, 2012 - 1:31am #8

For me it works fine to start with a fully Android version 1.5.10 and than just import the iOS package and deploy this one.

Best practice for both Android and iOS in single project

July 30, 2012 - 1:29am #7

DEL Double post (forum bug again)

Best practice for both Android and iOS in single project

July 30, 2012 - 1:28am #6

What i had: vuforia IOS 1.5.9 add Android 1.5.10 -> Script errors.

 

What works for me: Delete all vuforia IOS 1.5.9 files and then add Android 1.5.10 and then add IOS 1.5.9.

Kind of pain in komplex projects.

Best practice for both Android and iOS in single project

July 28, 2012 - 7:20am #5

Are you importing this version of the extension into a project that was originally developed using an earlier version of the extension? If so, you should remove the scripts from the earlier version and only use those from the current version.

Best practice for both Android and iOS in single project

July 27, 2012 - 1:23am #4

@ksiva: I tryed to only import the base package, but it does makes a lot script errors because in the 1.5.10 android version some and not all scripts are replaced.

Re: Best practice for both Android and iOS in single project

March 18, 2012 - 8:38am #3

With the current release the order shouldn't matter, they work off the same code base. It is important that when you import the second package that you only import the base package, not one of the sample packages. Importing multiple sample packages into a single project can sometimes cause problems.

- Kim

Re: Best practice for both Android and iOS in single project

March 16, 2012 - 12:40pm #2

for me it turned out to work well to import the package with the lower version number first. iOS --> 1.5.9 afterwards Android --> 1.5.10.
didn't give me problems the last time i tried.
best,
stefan

Log in or register to post comments