http://iscoresports.com/

I'm consistently getting an error message upon attempting an export on my iPad after updating to 3.35.215. I have tried resetting the device and relaunching the app. Unfortunately, I failed to do an export just prior to updating, and I have a few games on my device that have yet to be uploaded. The error message is long and somewhat cryptic, and I cannot cut and paste it, but it says something like, "cannot allocate memory" and "connection failed," or something along those lines.

Have you done a hard reset of iPad. Slide to off? ( hold power button till alide to off appears).

Try that..

IPad 1 or 2, base memory =?

I have iPad1 3G 30g and export with v 3.35 works fine...

Also, try iscorecast synch, on the games since last update..

if you can do that it can be a backup archive that we can later use to recover games if we don't find th fix and have to re install app. (last resort)

Thanks, Tex. It's working now, not sure what fixed it. Yes, I had already done a hard reset. It's an iPad 2 64G ATT 3G with tons of available space. I had been trying to update over 3G, which wasn't working. But when I got home a few minutes ago, it worked like a charm over my Wifi network. And I just tried 3G again just for good measure, and it worked as well. Strange...it went hours with numerous unsuccessful attempts, and now it works fine. Wish I knew what fixed it, but I'm happy it's working now.

Yeah!

Sounds like perhaps internet connection quality issue on 3G where you tried the first times..

I don't think this is an isolated issue. I get the same message and I never got it before upgrading to the 3.35.215. I'm getting it with 4 or 5 bars so connectivity isn't an issue. The stuff that made sense (to me) said "A connection failure occurred" and the underlying error said "The operation couldn't be completed. Cannot allocate memory." I should have plenty of memory. I have very little stuff on my phone (IPhone 4)

This is actually not a new issue. Prior to 3.31, we just displayed "Could not export at this time. Please try again later." We now show the full internal message.

Hmmmmm. Don't remember ever getting that message.