-
Notifications
You must be signed in to change notification settings - Fork 2.5k
Issues after application autoreload (1.4) #244
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
Comments
Same with me. Phonegap 3.6.3 and the new phonegap developer app result in deviceready not fired on my android 4.1 (Galaxy S3 Mini). Windows 7x64 |
I just updated phonegap to latest version: 4.1.2-0.22.9 and the issue disappeared. |
There is a major known npm 2.x issue when using @vancata glad to hear that you got it going! |
Well I use npm 1.4.3 and CLI 4.1.2-0.22.9. |
Same here. There is no autoreload if I build this app with |
@screendriver actually, autoreload is only a feature of the PhoneGap Developer App and the phonegap serve command. It's not included in compiled applications (although you could do that yourself with livereload). @whitecolor Are you experiencing the problem when running |
@mwbrooks I know this. You misunderstood: I compiled the phonegap developer app by myself and included some 3rd party Plugins that I need. Then I installed it on my android device and run |
@screendriver yep, I totally misunderstood! Hmmm... I'm not sure why your version is not working correctly. The PhoneGap CLI provides all of the logic for auto-reload. Before serving your app, it injects the auto-reload JavaScript, which pings the server. So as long as the |
@mwbrooks just try it yourself. Check out the master, run |
@screendriver Oh, you're referring to the Can you try checking out the As a backstory, we prototyped a new approach for delivering content from the CLI to the app. It was looking very good and we merged it into the master branch. Unfortunately, after merging we discovered a blocking issue in Android and had to rethink the approach. Today I'm actually reverting our changes to master, so that it's aligned with the latest code in the app store. |
@screendriver I've cleaned up the |
It works. Thank you! The only issue I have: I can't use 3rd party plugins that I have installed. Is there any registration or something I have to add the plugins? |
@screendriver awesome! I see you've created an issue (#252) to answer your next question. So I think it's safe to close this one off! @whitecolor if you're still having this issue, feel free to drop a comment and I'll reopen it! |
@mwbrooks Michael, I was trying to contact you about other issue by email, but wasn't succesfull to get the answer wan't it appropriate channel to contact you about PG related topic? |
@mwbrooks I still have the same problem with |
Hi @whitecolor, sorry about the slow e-mail response! I go through periods where I'm buried in e-mail and it's hard to keep up! I'll try to respond to you in a bit. Generally, it's better to ask questions in the public, rather than private email. Usually if you have a question, then someone else has the same question as well. So, it's better to workout the solution in the public, so that others can find it later on. For the |
@mwbrooks ok, thanks, the email question was about Media Plugin (playback rate) and I failed to get any public response in its repo. |
After autoreload (if some watched file changed) OR after restart of
phonegap serve
application running on the device reloads index.html, and there is a couple of bugs that were noticed:Sometimes (accidentally, but almost always in my case):
deviceready
event is not firing (on Android 4.1)file
andfile-transfare
) are not available. (iOS7)If to shutdown the app on device and lauch it again for first time everyting works fine (
deviceready
and plugins are available) after auto reload the app is broken.I encountered this on phonegap CLI 3.6 and 4.1 running on Windows 7x64 and on OS7 and Adroid 4.1 devices.
I don't know if its a bug of 1.4, currenty I didn't try on previous version of the app.
The text was updated successfully, but these errors were encountered: