Mobilinc crashing on iOS 9.3.5 with ISY 5.0.4 during Parsing program status.

[Xathros]

Hi Wes,

 

I've been having a problem for a while now where ML will quit shortly after launch.  On a cell connection, I can often do what I need before it quits but on WiFi its faster and fails before I can navigate to what I need.  I spent some time today trying to debug but wasn't able to get very far with it.

 

I deleted my profile and started fresh just to make sure there was nothing corrupted in my old ML/ISY profile but still have the same crash at the same point.  I'm sure it's something odd in my ISY that is tripping it up but I have no way of telling what it doesn't like.

 

I have:

ISY 5.0.4

iPhone 6S

iOS 9.3.5

ML v4.7/Advanced Locations/Extended Screens/IP Cams/Resource Mgr.

 

I can send you a crash dump from my phone if that helps.  Can you help me figure out whats going wrong here please?

 

Thanks in advance.

 

-Xathros

 

[InsteonNut]

Hi Xathros,

 

Thanks. This is a known issue with ISY 5.x alpha. There is a scenario where the Program XML becomes corrupted in the 5.x alpha which crashed the XML parser in MobiLinc. I've got this fixed so that MobiLinc won't crash, but it won't fix the invalid XML from the ISY.

 

I'm currently prepping a release of MobiLinc that includes a handful of fixes, including this, timed with the iOS 10 update due out here soon.

 

The only way forward as far as I'm aware is to downgrade your ISY back to 4.x and restore a known good backup of 4.x.

 

Wes

[smokegrub]

I have had the same experience with 4.3.26 and a Mac running 10.10.5. MobiLinc occasionally will not load and I have to reset my iPhone 6s before it will load, I have have also changed my profile with the same outcome.

[MWareman]

No app should crash from unexpected input data. A crashing app is an app with a potentially remotely exploitable vulnerability that just hasn't yet been properly researched and fleshed out.

 

You should probably check for valid XML, and throw a descriptive error instead of parsing it and risking an unhanded exception.

[Xathros]

Hi Xathros,

 

Thanks. This is a known issue with ISY 5.x alpha. There is a scenario where the Program XML becomes corrupted in the 5.x alpha which crashed the XML parser in MobiLinc. I've got this fixed so that MobiLinc won't crash, but it won't fix the invalid XML from the ISY.

 

I'm currently prepping a release of MobiLinc that includes a handful of fixes, including this, timed with the iOS 10 update due out here soon.

 

The only way forward as far as I'm aware is to downgrade your ISY back to 4.x and restore a known good backup of 4.x.

 

Wes

 

Thanks Wes.  

 

So if I wait for the next release, I can stay with 5.x and get around the crash correct?  I have way too much dependance on the 5.x branch with my node servers and extended variable usage to go back to the 4.X branch.  Have you submitted the update for approval already and it's held for the iOS 10 release today or does it still need to go through approval before we see it in the update list?  If delayed, any chance I can get back into your beta program?

 

Thanks again.

 

-Xathros

[InsteonNut]

Hi Xathros,

 

The next update doesn't require iOS10. It's a minor update fixing a couple of issues like this. Should have it submitted to Apple here in the next few days. I've got larger plans for the new features in iOS10 that I can leverage in MobiLinc but takes time to develop.

 

Please be aware that the fix allows MobiLinc to gracefully exit the Program XML parsing and to continue with the next syncing step. Any programs after the XML corruption won't be parsed or listed in MobiLinc.

 

Wes

[Xathros]

Hi Xathros,

 

The next update doesn't require iOS10. It's a minor update fixing a couple of issues like this. Should have it submitted to Apple here in the next few days. I've got larger plans for the new features in iOS10 that I can leverage in MobiLinc but takes time to develop.

 

Please be aware that the fix allows MobiLinc to gracefully exit the Program XML parsing and to continue with the next syncing step. Any programs after the XML corruption won't be parsed or listed in MobiLinc.

 

Wes

Hi Wes,

 

 

Sounds good.  Is there anyway to identify the affected programs so that I could delete and recreate them or is this a bug in 5.0.4 that is corrupting the XML output while the programs are actually fine within the ISY?  Is there a predetermined sequence in which the ISY outputs program XML?  I'm just looking for ways to fix or workaround the issue until it can be fully resolved.  Any guidance you can offer is greatly appreciated.

 

I will watch for your update on the App store and am excited to see what you come up with (down the road) for iOS 10's new features.

 

-Xathros

[InsteonNut]

Hi Xathros,

 

Unfortunately no. I'm not sure of what order the XML is in or how to communicate what didn't get parsed out in anyway that would make sense. For a fix or workaround the only thing I know is to downgrade back to 4.x and restore from a known good 4.x backup. Anything else and UDI would need to comment.

 

Wes

[Xathros]

Hi Xathros,

 

Unfortunately no. I'm not sure of what order the XML is in or how to communicate what didn't get parsed out in anyway that would make sense. For a fix or workaround the only thing I know is to downgrade back to 4.x and restore from a known good 4.x backup. Anything else and UDI would need to comment.

 

Wes

 

Understood.  Thanks.

 

-Xathros

[rafarataneneces]

Hi Xathros,

 

Thanks. This is a known issue with ISY 5.x alpha. There is a scenario where the Program XML becomes corrupted in the 5.x alpha which crashed the XML parser in MobiLinc. I've got this fixed so that MobiLinc won't crash, but it won't fix the invalid XML from the ISY.

 

I'm currently prepping a release of MobiLinc that includes a handful of fixes, including this, timed with the iOS 10 update due out here soon.

 

The only way forward as far as I'm aware is to downgrade your ISY back to 4.x and restore a known good backup of 4.x.

 

Wes

 

I don't think the XML becomes corrupted necessarily.

 

I just delete 3 folders

each one with 1 simple program

 

boom, every single MobiLinc in all my iOS devices stops synchronizing.

 

I am terrified to delete programs now.

[InsteonNut]

rafarataneneces,

 

I responded to this in your other post. For simplicity, and my support tracking, please open up a new topic in the future instead of posting about the same issue across old topics.

 

Wes

[InsteonNut]

Hi Xathros,

 

FYI: MobiLinc 4.8 was released by Apple today. It should now guard against corrupted XML. 

 

Wes

[Xathros]

Hi Xathros,

 

FYI: MobiLinc 4.8 was released by Apple today. It should now guard against corrupted XML. 

 

Wes

 

Hi Wes,

 

I installed the update this morning and am back in business.  I do think I found a bug in the IP Cam stuff though.  I was setting up my cams again and after the last step adding my first camera (confirm PTZ settings)  the cam just disappeared leaving an empty cam page.  I repeated the process and the second time around, it completed and showed the cam.  I notice now when selecting cams to associate with scenes and devices that that cam is listed twice.

 

Other than that, all looks good so far!  Thanks.

 

-Xathros

[InsteonNut]

Thanks Xathros!

 

Sounds like a dup got created. Should be able to delete that second one.

 

Wes

[Xathros]

Thanks Xathros!

 

Sounds like a dup got created. Should be able to delete that second one.

 

Wes

 

How?  I only see it listed once on the cam screen. Only place I see the dupe is on the list when associating cams to devices/scenes.

 

-Xathros