Repository navigation
Ionic Framework Lifecycle should wrap with vue ErrorHandler #30374
Description
lifecycle should handle error
I diff the lifecycle hooks code between ionic and vue,
it is better to wrap hooks with callWithAsyncErrorHandling as vue do.
no error handle
vue onMounted will hook onErrorCaptured, but onIonViewWillEnter not
- onIonViewWillEnter(async () => {
onMounted(async () => {
await init();
});common-class.ts:60 Uncaught (in promise) ApiResultError: Order has expired
at UseApiRouteFetcher.ts:107:15
at callHooks (ofetch.03887fc3.mjs:131:15)
at async $fetchRaw2 (ofetch.03887fc3.mjs:299:7)
at async $fetch2 (ofetch.03887fc3.mjs:316:15)
at async fetchTypedResult (typed-fetcher.ts:78:21)
at async ionicFetchResult (ionic-fetcher.ts:45:12)
at async init (prepay.vue?t=1745726446418:133:32)
at async prepay.vue?t=1745726446418:143:7
ionic lifecycle.ts
ionic-framework/packages/vue/src/hooks/lifecycle.ts
Lines 26 to 31 in c5c4d1d
vue apiLifecycle.ts
const res = callWithAsyncErrorHandling(hook, target, type, args)
// ....
return res
Activity
thetaPC commentedon Oct 14, 2026
Thanks for the report, and sorry for the delay.
Verified on 9.0.8. Ionic calls
onIonViewWillEnterand the other Ionic page hooks directly instead of through Vue's error handling, so an error thrown in them never reachesapp.config.errorHandleroronErrorCaptured. An async hook's rejection ends up as an unhandled promise rejection. A synchronous throw also stops the page transition, which leaves the new page invisible. The options APIionViewWillEnterand the other options API Ionic hooks have the same problem.Switching to
onMountedgets the error handled, butonMountedonly runs the first time the page is displayed. Ionic keeps pages in the DOM, so returning to the page later will not runinit()again.Tracked as a bug in
@ionic/vue.