-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash on IOS using Ionic 1.2.4 and cordova IOS 4.1.1 and wkwebview-engine #96
Comments
it could be a problem with cordova version, telerik version and wkwebview-engine version. Try without wkwebview-engine. What is the stack trace saying? |
Here is the stack trace. It's funny, it wishes good luck to us! May 3 09:13:09 iPhone YachtNeedsBeta[690] : THREAD WARNING: ['NativePageTransitions'] took '10.215088' ms. Plugin should use a background thread. |
Getting a ton of app crashes as well +1 |
I tried removing the wkwebview-engine plugin, the app freezes every time i click an ng-repeat with no errors in the logs: Ionic 1.7.14 |
You need to check the device log not the console if you want a hint. Once you have the error message you can create an issue on com.telerik.plugins.nativepagetransitions repository. |
I solved it removing everything and installing it again using wkwebview-engine-localhost instead of wkwebview-engine (I don't know if this is fixing something or not). Here is what I'm using:
This was my workflow to get it working:
|
I strongly recommend NOT to use this plugin |
Hi,
I'm trying to use this wrapper with:
Here the references
I'm using it with default settings (without doing anything else than istalling plugins and calling dist js in my index.html as for install instructions).
My app is crashing sistematically after the second native transition occurs.
This means that my app run, it make the first transition (I can see it is native) and then, when i try to go to another page, it crashes.
I'm facing this also changing ionic release with 1.2.4 and 1.1.1.
Have you got some hints about that?
Thank you.
The text was updated successfully, but these errors were encountered: