Closed
Bug 702162
Opened 13 years ago
Closed 13 years ago
android.content.ActivityNotFoundException: No activity found to handle Intent { act=android.intent.action.VIEW dat=file:///android_asset/www/error.html }
Categories
(Web Apps :: Soup, defect, P2)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: aaronmt, Assigned: Harald)
References
Details
/DroidGap(11457): Error loading url file:///android_asset/www/error.html E/DroidGap(11457): android.content.ActivityNotFoundException: No Activity found to handle Intent { act=android.intent.action.VIEW dat=file:///android_asset/www/error.html } E/DroidGap(11457): at android.app.Instrumentation.checkStartActivityResult(Instrumentation.java:1509) E/DroidGap(11457): at android.app.Instrumentation.execStartActivity(Instrumentation.java:1383) E/DroidGap(11457): at android.app.Activity.startActivityForResult(Activity.java:3165) E/DroidGap(11457): at com.phonegap.DroidGap.startActivityForResult(DroidGap.java:1495) E/DroidGap(11457): at android.app.Activity.startActivity(Activity.java:3271) E/DroidGap(11457): at com.phonegap.DroidGap.showWebPage(DroidGap.java:888) E/DroidGap(11457): at com.phonegap.DroidGap$5.run(DroidGap.java:1560) E/DroidGap(11457): at android.os.Handler.handleCallback(Handler.java:605) E/DroidGap(11457): at android.os.Handler.dispatchMessage(Handler.java:92) E/DroidGap(11457): at android.os.Looper.loop(Looper.java:137) E/DroidGap(11457): at android.app.ActivityThread.main(ActivityThread.java:4215) E/DroidGap(11457): at java.lang.reflect.Method.invokeNative(Native Method) E/DroidGap(11457): at java.lang.reflect.Method.invoke(Method.java:511) E/DroidGap(11457): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:784) E/DroidGap(11457): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:551) E/DroidGap(11457): at dalvik.system.NativeStart.main(Native Method) -- Samsung Nexus S (Android 4.0) origin/HEAD (6e9a13a)
Comment 1•13 years ago
|
||
Could we get more details on when this crash occurred. It's very hard to pinpoint a problem based on stack trace alone without any context.
Comment 2•13 years ago
|
||
Aaron an update here ?
Comment 3•13 years ago
|
||
Any steps to repro would be great !
Reporter | ||
Comment 4•13 years ago
|
||
I'll see if I can reproduce this; basically the application got into a state where I was unable to view anything. It looks like there's no activity to handle the exception/error?
Comment 5•13 years ago
|
||
This will get worked on later .. closer to release i imagine after all features have landed
Priority: -- → P2
Assignee | ||
Updated•13 years ago
|
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 6•13 years ago
|
||
Harald, please confirm if you landed a fix for this, and close if so.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 7•13 years ago
|
||
Shortcuts don't use this handler anymore.
Status: REOPENED → RESOLVED
Closed: 13 years ago → 13 years ago
Resolution: --- → FIXED
Comment 8•13 years ago
|
||
verified, haven't seen this on the app, and pretty sure a non issue
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•