getting strange error when submitting to iTunes Connect - iphone

I am on the last stage of my upload, and i clicked submit, only to receive the error;
There was an error saving changes: NullPropertyException. Stack is: [Ljava.lang.StackTraceElement;#5528cffb
what does that mean?
I am 99% sure I built correctly.
the error changes ( the # bit) after a refresh and click of submit again.
Help me out please!
Sam

Apple's websites all run on WebObjects, which is Java based. Hence the Java error. This is almost certainly a problem on their side. I'd try submitting again tomorrow and if it still fails, contacting their support.

Related

PageExpiredException occurs after closing of ModalWindow

Currently I'm trying to upgrade the application from wicket 1.4 to wicket 6 and I'm stuck with the following issue:
When I try to close ModalWindow, it is closed but I receive PageExpiredException on the page where I was opening this ModalWindow, so I'm redirected to
/myapp/wicket/bookmarkable/org.apache.wicket.markup.html.pages.PageExpiredErrorPage
I thought maybe the way I create ModalWindow is outdated, so I've tried an example from here
http://www.wicket-library.com/wicket-examples-6.0.x/ajax/modal-window?0
and it gives me the same exception.
Maybe I have to configure something in my WebApplication implementation, but I don't know what.
If anyone could help, it'll be really appreciated. Thanks.
Check your server logs for errors related to the serialization of the opener page. PageExpiredException means that the page cannot be found in the page storage. If there was an error with the serialization then it won't be stored and thus later won't be found too.

When trying to run the Audio/Video widget (based on the GoRTC library), i get a "...was interrupted while the page was loading" error

I Googled the error and tried some of the suggestions, to no avail. This happened inside FireFox Aurora 29.0a2 on Windows, but i also got the same thing in Chrome on a Mac.
Any ideas as to what's causing this? Thank you!
The error will not affect the GoInstant service in any way. The error is logged by the browser for previous connections that are now disconnecting/interrupted on page refresh.
In other words, when you first connect in a fresh browser you will not see the error because you have no prior connections. Once you refresh, that first connection will be "interrupted" and you will create a new connection to GoInstant.

Hosted app: “Installation of this item may not work properly”

My hosted app is showing a floating banner with a notice saying “Installation of this item may not work properly.” on its Google Chrome Web Store product page. The app is undiscoverable by searching the Web Store.
What is causing this problem? I find no additional information in the developer dashboard.
If you get this message, it is probable that there really is an error in the manifest or locale files (For example, in my case it was a trailing comma on the locale files).
The process y follow to solve the problem was:
Try to instal the app version you have just submited to the chrome store. When you try to install the app you will probably get a error message thats points you on the track of the problem of your manifest file.
Solved the problem on the app and upload it again. You may get the same error on the developers panel. Two thinghs can be appening:
A) If you've already corrected all errors in the manifest files remenber to publish the changes and what is more important remenber that the publication process may take a few minutes to become effective. The message will disappear after a while if everything is okay. (This explains why is you look on the internet for that problem you find people saying that the message will disappear after a while)
B) If error persist event after the publishing process have been complete finished. You may have not solved all error on the manifest file go back to Step 1
cheers
I had this exact problem. When I tried installing, I got an error message about a missing file.
When I removed my locales directory, everything worked fine.

iCloud and GEOResourceManifestServerRemoteProxy: Lost connection to geod warning

I am testing my app that uses iCloud. Sometimes, when I fire up the app I get the following warning in the console:
GEOResourceManifestServerRemoteProxy: Lost connection to geod
Once I get this warning I don't seem to get any data from iCloud. I have tried searching this issue, but have found very little information on it.
Any suggestions on how one should try to detect this issue and try to handle it?
I realize that you asked this back in March, but according to this it can happen when a login (like a connection to FB) has timed out.
If you do a stacktrace and see , then this should help.
And here is the code for that interface, if that's helpful.

Weird Error from Xcode Debugger

I am using SQL lite database in my iPhone app. I have a refresh button on my Home screen and upon click of then refresh button I parse data from my web service and store the results into a SQL lite database. When I click on refresh button repeatedly I get an error. The error occurs after a variable number of clicks/refreshes each time. The error is:
Failed to load debugging library at:
/Developer/Applications/Xcode.app/Contents/PlugIns/GDBMIDebugging.xcplugin/Contents/Resources/PBGDBIntrospectionSupport.A.dylib
Custom data formatters are disabled.
Error message was: 0xe00805 "dlopen(/Developer/Applications/Xcode.app/Contents/PlugIns/GDBMIDebugging.xcplugin/Contents/Resources/PBGDBIntrospectionSupport.A.dylib, 10): image not found"`
After this error, my app crashes and when I logged the error it gives me an error "Unable to open database"
Please help me to resolve this error.
Thanks
Sandy
It would appear that the debugger is having a problem loading the data formatters that create the displays for various datatypes in the debugger window's variable display panel. If you've added any customer formatters, you should remove them.
Try running the program without the debugger and see if you get a crash. If so, the problem is in the app. If not, it's most likely in Xcode itself. I would test a dummy project and see if you get the same error.
It's possible there is hellish recursion somewhere in your code. I have seen that bring the debugger down but not with this error message.