Reef Angel Forum

Curt, I even tried to your development ones and same thing. It pops up Mem updated more than it did mine and then when I refresh it's the same values. I know if I refresh manually on the controller and go back into the screen it refreshes properly, but from my perspective this is not working at all. I did some debug and the URL is working properly, but the debug is not showing me enough data in the actual send part.

lnevo wrote:Curt, I even tried to your development ones and same thing. It pops up Mem updated more than it did mine and then when I refresh it's the same values. I know if I refresh manually on the controller and go back into the screen it refreshes properly, but from my perspective this is not working at all. I did some debug and the URL is working properly, but the debug is not showing me enough data in the actual send part.

Very interesting. I'm not quite sure what is going on with it then. I just know that when I looked at the code for custom locations a while ago, I saw that it was hard coded to be /mb. Will have to look into it further then.

Not sure about the plans for reefangel and iOS 7 - I'm running the beta 2 and the app doesn't work......the fields do not populate

My company just signed up as dev's so will see if its easy enough to update

I am also having the same issue with ios 7

Anything change server side Roberto? Like the XML or? After a YEAR of pain free iPhone app...I'm cursed with "could not download" on the original app. The specs screen (initial loaded) is 100% good with the initial load of the app but the relay page fails and then crashes the app. I'm stumped! it is ONLY the relay page that crashes the app. What in the world?

Not sure what would cause the crash, but we are always adding new XML tags.
There was about 20 added in the the past couple releases.

I'm going to guess its the app's interpretation of the XMLs. It's probably maxed out. So just a heads up for everyone...odds are iPhone app is officially outdated.

You know what, I've been having the same thing..i thought it was my bad wifi network... Its intermittent though. I'll have to look at the simulator and see what i can figure out.

If I'm persistent I can get them to load but about only 20% of the time. However when I override a relay (crash!)

So it's hard to know what is going on...

If i switch off wifi it works better..

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?