-
Notifications
You must be signed in to change notification settings - Fork 10
AR world launches before device support check. #3
Comments
- init() now uses promises. This ensures that all the steps of the init process are executed in the right order (this is needed for the ready() method which rely on the initialized flag) - The ready() method allows developers to write code that will be executed when Ionicitude is fully initialized These modifications should solve issue #3
As a complement, it should be noted that this problem occurs only when trying to launch an AR World right when the app starts. In any case, the commit 49a6862 should solve the problem. It adds a new method to Ionicitude, the Ionicitude.ready(function() {
Ionicitude
.launchAR('myAR')
.then(function(success) {
// React to successful launching
}
.catch(function(error) {
// React to unsuccessful launching
}
}); It also changes a little bit the To test that this solution is convenient, please download the latest version on the dev branch. If this solves the problem, please report it here so that I can close the issue, update the doc and push these modifications to the master. Thanks for your support 😉 |
Fantastic, it’s working great. Thank you so much. |
Ionicitude is a great solution which will make all the ionic dev's lives simpler.
I have noticed a slight problem which causes the app to crash due to unsupported feature error. The AR world launches before the device check is confirmed to be supported.
Please address this issue.
Thank you.
The text was updated successfully, but these errors were encountered: