Android: Deviceready has not fired after 5 seconds

deviceready has not fired after 5 seconds. ionic 1
ionic 4 deviceready has not fired after 5 seconds.
ionic native: deviceready did not fire within 5000ms
capacitor deviceready has not fired after 5 seconds.
ionic native: deviceready not fired
deviceready cordova not firing
cordova-plugin-device
ionic native: deviceready event fired after

After update Cordova to v6.4.0 and Android platform to 6.0.0, my app don't work any more. I'm getting this:

deviceready has not fired after 5 seconds. cordova.js:1223
Channel not fired: onCordovaInfoReady cordova.js:1216
Channel not fired: onCordovaConnectionReady cordova.js:1216

I tried to remove all plugins and add it one by one. I found that is a problem with cordova-plugin-device and cordova-plugin-network-information. All my plugins are up to date

If you happen to be running the Crosswalk plugin in your app I just confirmed that uninstalling it and reinstalling via;

cordova plugin add https://github.com/crosswalk-project/cordova-plugin-crosswalk-webview

Gets rid of

deviceready has not fired after 5 seconds. cordova.js:1223 Channel not fired: onCordovaInfoReady cordova.js:1216 Channel not fired: onCordovaConnectionReady cordova.js:1216

You can see the issue at Crosswalk's Jira issue listing here.

https://crosswalk-project.org/jira/browse/XWALK-7422

bug: deviceready has not fired after 5 seconds · Issue #259 · ionic , Platform: android 4.4 browser. With last stable versions of crosswalk, ionic and cordova, got "deviceready has not fired after 5 seconds" error deviceready has not fired after 5 seconds. cordova.js:1154 Channel not fired: onFileSystemPathsReady and again, reloading the page from chrome remote inspector, solves the problem and the page loads and works fine.

This should be fixed in cordova-android 6.1.0. It has not been added to the npm-registry yet, so you can use it by placing this to your config.xml:

<engine name="android" spec="https://github.com/apache/cordova-android.git#6.1.0"/>

console.log: deviceready has not fired after 5 seconds. · Issue #2262 , After update to the new cli it's taking a long time to refresh the code using ionic cordova run android --livereload -c -s. I've tried to reinstall all my  Hello, I would like to know if there is a problem with this 7.1.4 android version as I keep having this issue in my chrome://inspect console: deviceready has not fired after 5 seconds. cordova.js:1

Solution:

put the call "cordova.js" to the last line in the page.

<script type="text/javascript" src="cordova.js"></script>
</body>
</html>

Greeting...

Deviceready event not firing in Android DevApp (deviceready has , The app will open after a few seconds, but the ready() code won't run. > ionic serve -c --no-open. Starting app-scripts server: --address 0.0.0.0 --port 8100 --  cordova.js:1183 deviceready has not fired after 5 seconds. cordova.js:1176 Channel not fired: onFileSystemPathsReady. it works fine if I just install one of these two plugin. maybe the cordova-HTTP use old version of org.apache.cordova.file and conflict with new version of org.apache.cordova.file

I recently encountered this same issue on iOS. Eventually what worked for me was a simple remove and add of the ios platform:

cordova platform remove ios
cordova platform add ios

It had been quite a while since I had completely re-built the ios platform and, just like you, I had made other major changes during that time (Cordova upgrade, XCode upgrade, etc). My theory is that my config.xml or existing ios build was somehow incompliant with the latest Cordova requirements. Doing a platform remove and platform add will clear out the build files and update config.xml.

I doubt this applies to the OP, but for others who've encountered this same issue, please ensure that you've included cordova.js in your index.html file. If you've not done so, add this line:

<script src="cordova.js"></script>

It's a very common omission when just getting started with Cordova.

Solved: IOS: deviceready has not fired after 5 seconds., IOS: deviceready has not fired after 5 seconds. Avatar after 5 seconds. Channel not fired: onCordovaConnectionReady It looks like something has changed on the PGB side. I also tried And in fact it seems worse on Android. Likes. Like. Solved: Since today I get the following errors when starting the app in IOS: deviceready has not fired after 5 seconds. Channel not fired:

deviceready has not fired after 5 seconds : Wikitude, Developer App on my Android tablet: deviceready has not fired after 5 seconds​. Channel not fired: onPluginReady. Channel not fired: onCordovaReady Hi, The app is still having the problem (white screen after boot (with/without splash)), but today I'm getting this log in Debug console!: deviceready has not fired after 5 seconds. Channel not fired: onPluginsReady. Channel not fired: onCordovaReady. Channel not fired: onCordovaConnectionReady.

Solution to PhoneGap issue: 'device ready has not fired after 5 , Solution to PhoneGap issue: 'device ready has not fired after 5 seconds' 1) add the platforms with cordova platform add ios android. cordova deviceready not fired after 5 seconds (plugin v4.0.2) #142. daniprofe opened this issue Jul 19, 2017 · 6 comments. My app hangs at init and never starts (cordova deviceready event not fired). After removing the plugin everything goes ok. Console log: deviceready has not fired after 5 seconds.

Deviceready has not fired after 5 seconds - mobile, Hi I created a simple app from the meteor tutorials for running on iOS device using meteor create hello meteor npm install and then run on iOS  After update to the new cli it's taking a long time to refresh the code using ionic cordova run android --livereload -c -s. I've tried to reinstall all my plugins and nothing. I've even tried to start a new blank app via ionic start blank and when I run on my android using --liverealod it's happening the same thing.

Cordova deviceready has not fired after 5 seconds in sencha touch , Android console prints a message like "deviceready has not fired after 5 seconds​" and "Channel not fired: onCordovaInfoReady". deviceready has not fired after 5 seconds Be/Created -ios true -android true I do get the "Wikitude Plugin" index.html to display, but clicking on the links don't

Comments
  • I'm having the exact same issue...
  • That was on mac, now I'm trying on a PC, and is worst...
  • The problem is with those plugins (cordova-plugin-device && cordova-plugin-network-information). Those plugins fire the onCordovaInfoReady and onCordovaConnectionReady "channels" respectively. If they don't fire, then deviceready doesn't fire. Must be something that changed in cordova-android 6.0.0, which is preventing those plugins from firing their channels...
  • I couldn't see anything. I've since downgraded to cordova-android 5.2.2, and that seems to work OK, even with cordova 6.4.0. Maybe try that for now.
  • @asgeo1 what about iOS, i'm getting white screen, I tried fallback to iOS 4.2.1 and is still happening..
  • When switching to cordova android 6.0.0 the primary bridge was changed to the EVAL_BRIDGE. Crosswalk adds that support in version 2.2.0 github.com/crosswalk-project/cordova-plugin-crosswalk-webview/…
  • Thank you, I'm gonna wait the official release
  • 6.1.0!! a lot or bugs I supose...so bad, cordova makes me lost 3 days
  • I just updated to 6.1.0 via command line platform remove and platform add. It fixed an issue with seeing the default Cordova icon as my splash screen instead of the one I had setup. But the splash screen doesn't hide unless I force the app to the background and then re-open it. Also the deviceready has not fired after 5 seconds and Channel not fired: for onCordovaInfoReady and onFileSystemPathsReady messages continue to show up in my console.
  • Thank you so much. I was fighting issues with icons, splashscreens, deviceReady events, push notifications, and much much more on Android. I went with 6.1.1 and thsi fixed everything!
  • @YokeshVaradhan There is not, I normally add it to the end of the config <engine name="android" spec="https://github.com/apache/cordova-android.git#6.1.0"/> </widget>