[bayamo]

edited july 23 (wayne) – this issue is fixed in the GapDebug 2.0 release

I have just installed GapConnect on a Macbook Pro running 10.10.4. Whenever I “Open Debugger”, the browser window keeps reloading with a popup stating “GapConnect Connection Lost” “Restart GapDebug to resume debugging”. I can see the GapDebug in the background greyed out and can even see both my iPhone and iPhone simulator in the background. If I plug in and unplug my phone, I can see the changes in the greyed out background. I have attached a screenshot.

I have tried running with both Chrome versions 43.0.2357.134 and 41.0.2272.89.

Can you help me?

• This topic was modified 9 years, 5 months ago by wayne. Reason: fixed

Attachments:

You must be logged in to view attached files.

[bayamo]

I have attached the log file.

[wayne]

@bayamo
Thanks for sharing this issue with us. Chatting with Vadim (gapdebug developer) we have implemented a fix for this issue that will be included in the 2.0 update planned for early next week (monday or tuesday).

[bayamo]

That’s great. Can you post when you release the version that fixes the problem?

Regards,

Frank

[wayne]

Absolutely will update this thread when the production version is ready.

Would you be interested in trying an early version (today’s build) and giving us feedback if the problem is resolved in your env?

[bayamo]

Sure, would be happy to.

[wayne]

Here are links to the latest build today. This version will install under the name GapDebug-Dev-Branch. While it will not impact your current GapDebug installation, I recommend you uninstall GapDebug before installing this internal build. Lastly please let us know asap if you hit a snag or can replicate the problem. Oh and have a great weekend. I’ll check in as often as I can this weekend.

Mac OSX installer
https://dl.dropboxusercontent.com/u/26766004/GapDebug-Dev-Branch-2015-update-2.0.20150717-installer-macosx.dmg

Windows installer
https://dl.dropboxusercontent.com/u/26766004/GapDebug-Dev-Branch-2015-update-2.0.20150717-installer-windows.exe

[bayamo]

Good news, 2.0.20150717 solves the problem. I will now start using it to see if there are any other problems.

[wayne]

That’s great news. Just made my friday 🙂
Thx for test driving the dev app. This is the final version unless we find an issue late in our final round of testing. We are updating docs and video for the release now.

[bayamo]

🙂
I’m having trouble connecting to a PhoneGap app. I can see the phone, but when I start a PhoneGap app, it does not show up in GapConnect. Going through the documentation to make sure I’m not missing something.

[wayne]

See the app requirements at the top of this doc https://www.genuitec.com/products/gapdebug/learning-center/configuration/

If you are debugging an ios app, the app must be signed with a developer certificate and profile (apple’s rules not ours).

If you are debugging an android app there is a property that needs to be set (section 3.2 in the doc).

[raymondcamden]

Ok, I can confirm the dev branch fixes the infinite reload issue – but I also have the same problem as bayamo. I’m confused – what changed in regards to needing to sign the app? If I connect w/ Safari, I can debug my Cordova app just fine. Why does GapDebug now need something new?

[wayne]

hi ray,
Thanks for sharing feedback about the fix. Glad to hear it is working consistently for multiple beta testers.

> what changed in regards to needing to sign the app?

I’m trying to understand if there is an ios glitch in the beta that I’m overlooking. There have been no requirement changes. An app that is debugging in GapDebug 2015u1.3 (current) should be debuggble in the 2.0 beta with no additional changes. Are you seeing running ios apps fail to appear in the GapDebug device panel that are visible in the Safari webkit inspector? If yes:
0) please try unplugging device usb and reconnecting to see if there is a commo glitch with the device
1) would you please share build details about what type of cert/profile are used to create the app
2) are using the XCode 7 beta
3) are you running OSX El Capitan beta

The note above to @bayamo is a reiteration of existing app debug configuration requirements. It does not introduce any new ios app build requirements. Apple has always required apps to be signed with a developer certificate and profile to be debuggable. I’m wondering if there is something goofed in the beta that I’m missing.

[raymondcamden]

Hmm. Well, it is definitely not working for me anymore. They definitely show in Safari. I’m using the simulator, not a real device. Not using XCode 7 and not using El Capitan.

cert/profile: This is a virgin Ionic project I’m using to test. No cert outside of what XCode uses to sign local projects. I’m not entirely sure how that works. 😉

But to be clear, worked before, not now. 🙂 (Well, worked before until this infinite reload issue.)

[wayne]

Thx, your help appreciated.
Investigating. Will follow up as soon as I know more.

[Author]

Posts