For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 4 replies, 4 voices, and was last updated 13 years ago by
.
-
Posts
-
Hi,
For two days now I am not able to build any versions of the MOBI programs I have. These are programs that were working fine until two days ago. It started with very long build cycles with no response for a very long time (over 1/2 hour) which used to get done in a few mins. After waiting till I received a message instead of cancelling, I started getting error.log messages that said: “Unable to build application; application size is too big or server is too busy now.”
These were all happening under MOBI2.3 in WIN7.
Then I read about the 2.5 changes and upgraded to that hoping for a relief. The same thing is happening in ver2.5.
Then I decided to test something very simple. I wrote a one button program that when pressed displayed a message in a text field. It ran fine in the emulator / test center. Then I tried to BUILD it and the same thing is happening: waiting for over 1/2 hour and receiving error.
The last test MOBI size is: 265215 (It is attached)
IOS Build # 7632091
error.log (attached)I tried the same BUILD in ver 2.3 in another installed machine just to test and received the same error.
Any help or explanation is appreciated.
TG
hi if you look we have already started a thread for this, it seems that MobiOne’s server may be having problems we are awaiting MobiOne to advise
Thanks Tech Support,
Seems like things are back to normal. Cranking out code from the new 2.5 release without a problem again.
The new debug environment is very nice. I was using the Chrome one for local testing for a while. It is great to have it integrated into the MOBI test center.
I love the fact that now I can point to a part of the design in the test center and have it locate the code under it. Makes things very fast in troubleshooting.
TG
Hi tguneysu, all:
Yes, the issue has been resolved. More information in this announcement. Thanks again for reporting the issue and following up that things have come back to normal.
