- 7 Posts
- 0 Reply Likes
Posted 4 years ago
Petra V., Champion
- 7794 Posts
- 1391 Reply Likes
What is throwing that error message? A debugger? Your app (under hydration)?
If the latter, did you make a config change prior to your last Build?
If the latter, did you make a config change prior to your last Build?
- 7 Posts
- 0 Reply Likes
My app under hydration. I had made config changes, so I reverted back to a version that was confirmed working yesterday and now have the same issue like build is caching the bad config or something.
Petra V., Champion
- 7794 Posts
- 1391 Reply Likes
Please note that config changes are ignored by PGB when hydration is switched on. So, when changing config, switch off hydration, then build.
- 7 Posts
- 0 Reply Likes
Tried that as well, I failed to mention that. Turned off/on every combination of debugging and hydration, same error.
Petra V., Champion
- 7794 Posts
- 1391 Reply Likes
That can't be the case. If you switch off hydration, it can't be issuing this message.
- 7 Posts
- 0 Reply Likes
Let me re-phrase, I turned them off, did a build, then turned hydration back on and same error.
Petra V., Champion
- 7794 Posts
- 1391 Reply Likes
- 7 Posts
- 0 Reply Likes
Let me quickly just go over how I got this:
1) Yesterday I had a fully working build w/ hydration & debugging enabled.
2) Today, I made a config change (apparently improperly) so that when I tried the hydration update, I recieved that error above.
3) I turned off debugging / hydration and installed a build on my phone where it would work properly.
4) I went back into pgb and turned hydration back on and tried to load it back up on my phone, where I still continue to get this error.
1) Yesterday I had a fully working build w/ hydration & debugging enabled.
2) Today, I made a config change (apparently improperly) so that when I tried the hydration update, I recieved that error above.
3) I turned off debugging / hydration and installed a build on my phone where it would work properly.
4) I went back into pgb and turned hydration back on and tried to load it back up on my phone, where I still continue to get this error.
Petra V., Champion
- 7794 Posts
- 1391 Reply Likes
So, "something" is getting Hydration off stride, while your app works as expected without Hydration?
And all you get is a message "Whoops....", without further explanation of what went wrong? And does that happen prior to the splash screen appearing?
And all you get is a message "Whoops....", without further explanation of what went wrong? And does that happen prior to the splash screen appearing?
- 7 Posts
- 0 Reply Likes
Petra V., Champion
- 7794 Posts
- 1391 Reply Likes
Almost looks like Hydration isn't fully available at this time.
What PGB version are you using?
(btw: it's late at night here in Europe. I'll be back tomorrow)
What PGB version are you using?
(btw: it's late at night here in Europe. I'll be back tomorrow)
(Edited)
- 7 Posts
- 0 Reply Likes
Yeah, I saw a solution to a similar issue where they said debug was down on another thread, which is why I started off with "I believe either hydrate or debug are down or not working".
cli-5.2.0
cli-5.2.0
Related Categories
-
PhoneGap Build
- 15111 Conversations
- 275 Followers



