Reef Angel Forum

Not me. Same spastic result? Must be XML related because I get the error message about 4 or 5 times before it crashes. I think it's trying to read the additional/new XMLs.

I just tested the app on my wife's ipad and it is working just fine.

Totally random crashing on my end. Only applies to the relay control screen. The iPad app is written a little differently than the iPhone.

Trust me...I'm confused because I was the one who assumed it was other's configs when in-fact the odd app behavior is happening to me.

The XML code is the same between the ipad and iphone app.... all the back end code is shared.

The test is not a good one Roberto, it is very intermittent. I could be fine all day then suddenly have issues. Drew, have you tried switching the network connection when you are having issues. I find that's the only way to help it, but its still not perfect... I could be crashing 100% on wifi and then go to LTE and get 50/50... then next day 100% on LTE, I switch to wifi and it's better.

It's actually getting a little annoying. I need to take a look at the code and see what's going on, but since I can't easily recreate it and my simulator will only be on the network... it's going to be a tough nut to crack, unless someone is good with IOS and XML parsing

I've tried network swapping. Wifi/ethernet(simulator)/3G....I can't begin to put a % on my crashes...it's that random for me no matter the connection type

The MOST confusing part for me is: other users reported issues...all the meanwhile...nothing wrong on my side for a year or so...then randomly....crash, crash, crash

Yeah, I think it was the 1.0.9 as well. I never had a problem and now it's awful..

lnevo wrote:Yeah, I think it was the 1.0.9 as well. I never had a problem and now it's awful..

I wonder if this also has something to do with people getting more Timeouts using the android app as well? It could be unrelated though.

Drew does it crash for you in the simulator?

There was also new xcode announced and did we have any recent ios update? I know there was an itunes and xcode (non beta) added...

Curt or anyone that can try, id love to know if its just phone or if it can be reproduced in xcode...

When i can get a few I'll try and see...

Curt, i wouldn't discount any possible relation also a lot of reports about ph probes...maybe some underlying timing change be affecting?

Not exactly a crash in sim but the error message did pop up over and over until I had to close the sim.

lnevo wrote: Curt, i wouldn't discount any possible relation also a lot of reports about ph probes...maybe some underlying timing change be affecting?

It's hard to say. I'll just keep an eye on things and see what all comes about.

Just to add to the confusion. Upgraded from iOS 5.1.1 to 6.1.3 and I experience 50% less crashes (approx) than before. Now that's just odd...

So, here's the error that popped up in the simulator when I tried it. Crashed immediately...

This line is the one generating the error So it's definitely something in the xmlParser class that is doing it... reviewing that code next..

Have you tried to increase the flush size on the wifi attachment?
I post somewhere in the last couple days.

No can you post again and I'll try

I didnt see anything in the ios code restricting how much data to read etc...

I'm curious to know what you have right now.
So before you change, grab the "get e" dump.
http://forum.reefangel.com/viewtopic.php?p=29662#p29662

It was 450. Now it's 1420.

That was it... no more issues. So not a code problem... whew

Curt, can we get the current version submitted now Can't wait for my fixes to be in place

Awesome!!!
Yeah, 450 was enough for when we started and now we have so much info packed into the XML data that we need more room in the TCP packet
Both Android and iPhone seem not to like the fragmented packet.
Internet browsers and the Portal don't mind it though.

So this correlates with the android timeout then also?

Not the timeout. Android doesn't crash. It reports SAX parser error.

lnevo wrote:It was 450. Now it's 1420.

That was it... no more issues. So not a code problem... whew

Curt, can we get the current version submitted now Can't wait for my fixes to be in place

I am in the process of figuring out how to go about that process plus differentiating between this newer version and the existing version.


Sent from my iPad

Well my ios "training" has been out on hold, so I hope someone has managed to fix ios 7 issues :p otherwise the app will be redundant soon enough

redundant? i think you mean obsolete..

We still have until the fall before iOS 7 is going to be widespread. I'm 100% sure that most of the issues will be resolved when a release candidate comes out for iOS 7. Until then I wouldn't worry too much. My brother is doing the beta for iOS 7 and apparently many apps are broken. Apple won't release it if it breaks a lot of their 1billion apps on the app store...

lnevo wrote:redundant? i think you mean obsolete..

We still have until the fall before iOS 7 is going to be widespread. I'm 100% sure that most of the issues will be resolved when a release candidate comes out for iOS 7. Until then I wouldn't worry too much. My brother is doing the beta for iOS 7 and apparently many apps are broken. Apple won't release it if it breaks a lot of their 1billion apps on the app store...

Lol, yes that's what I meant.

I really really hope so and that Apple aren't just relying on Devs to update their apps with ios 7 compatibility.

I seem to recall something similar with ios 6, a lot of apps would randomly crash until they were updated

What is going on with the iPhone app now it stuck on updating I deleted the app and download it again and same issue.

Did you change the flush size on your wifi module?

Anyone else getting some weirdness in iOS 7? Temp reading works about every other refresh as do the on/off status bars on the outlets.

Yes its broken. No ETA.

Correct. No ETA. I'm looking at the code now and just trying to follow along with it. It's a little confusing to a non-ios programmer. Regardless, when the app is updated, unless wolfador updates it (which is doubtful), the app will be released under a different signature.