Build server keeps giving me the same old version...

Solar2D Daily Builds and Public Releases
#1

I have an urgent show-stopping bug on my hands that could possibly be an easy fix for you. Every time I build my app, no matter what resources, code, or settings I change, I get the same old version back form the build server. It is not a problem in me transferring the app. Believe me, I have spent long amounts of time debugging by looking on my end. I can’t say what caused this, it just started happening during routine device testing.

If an Ansca employee could just clear my server cache (there’s got to be one if this is happening), this would probably go away. I feel like as a paying subscriber, I deserve 30 seconds of your time for you to hit a button (or maybe delete some files).

Thank you for providing such a convenient, easy platform to develop with, and I hope to use you for all of my future apps (provided they will actually build). [import]uid: 7581 topic_id: 9777 reply_id: 309777[/import]

#2

Join irn irc.freenode.net and channel #corona

seanh-ansca is usually there are able to fix these kinds of issues. He’s going to hate me lol. But seriously, interactively fixing these issues is the best way - you can build, he can watch the log. [import]uid: 8872 topic_id: 9777 reply_id: 35643[/import]

#3

Same thing here too… we have remote XML Files which we download and file-depencies from that xml too… everytime our new xml-file is overwritten from a mysterious source with an old one, no longer online (we doublechecked and cleared every system cache, sandbox dir, project dir, ftp-dir, de- and reinstalled corona etc. etc.)

I really guess there’s some ansca-server related cache somewhere. If there is, it would be nice to have some kind of a “flush buildcache” button in the corona interface. [import]uid: 12870 topic_id: 9777 reply_id: 37791[/import]

#4

Hmmmmmm…

Something strange going on here. See my post:

http://developer.anscamobile.com/forum/2011/05/23/cant-test-multiple-apps-ios-device [import]uid: 9936 topic_id: 9777 reply_id: 37798[/import]

#5

Ok… we fixed the problem in our case. Just added “?” and a random math-string to the url - as I was used to do in Flash for certain file downloads.

For example “http://www.myurl.com/myfile.xml” becomes "http://www.myurl.com/myfile.xml?"..tostring(math.random()) and the caching troubles are gone.

Maybe this will help you mappum? [import]uid: 12870 topic_id: 9777 reply_id: 37890[/import]