iPhone 3.0 OS compatibiliy
by BeyondtheTech · in iTorque 2D · 05/02/2009 (6:14 am) · 35 replies
Has anyone tested their iTGB-built games on an iPhone running any iteration of the OS 3.0 beta that's out for us developers?
I don't know if this is premature to ask, but will iTGB support or take advantage of any of the new features of the OS 3.0, or is iTGB primarily independent of what the OS does?
I don't know if this is premature to ask, but will iTGB support or take advantage of any of the new features of the OS 3.0, or is iTGB primarily independent of what the OS does?
#2
05/03/2009 (2:05 pm)
3.0 support will be added to iTGB after 1.2
#3
According to the apple email sent today to developers all app that are not compatible with Firmware 3.0 will not be accepted in the appstore. So ?
What's about iTGB ?
05/07/2009 (2:08 pm)
Hi michael.According to the apple email sent today to developers all app that are not compatible with Firmware 3.0 will not be accepted in the appstore. So ?
What's about iTGB ?
#4
05/07/2009 (2:21 pm)
OS 3.0 being after 1.2 is fine. Just get 1.2 out the door and let us start using it and then do a quick release of 1.3 that only adds support for iPhone OS 3.0
#5
05/07/2009 (2:23 pm)
With the news and beta 5, I think 3.0 issues must be looked into ASAFP. I'm probably going to have to risk an upgrade now :(
#6
can use the majority of applications without any problems.
Affected were mainly "illegal" apps, ie apps that used undocumented api or used other irregular stuff that just bomb.
From Beta 5 its no longer optional to have a OS3 device, at least unless your release target frame is in August so you can wait till the june/july release of the real 3.0 and test it on that fully again.
05/07/2009 (3:09 pm)
I've had OS 3 since beta 1 on my itouchcan use the majority of applications without any problems.
Affected were mainly "illegal" apps, ie apps that used undocumented api or used other irregular stuff that just bomb.
From Beta 5 its no longer optional to have a OS3 device, at least unless your release target frame is in August so you can wait till the june/july release of the real 3.0 and test it on that fully again.
#7
05/07/2009 (6:06 pm)
I was hoping 1.2 will be compatible with sdk/os 3.0. It kinda sucks if it we have to wait for for a while after 1.2 to release anything
#8
05/08/2009 (7:30 pm)
Hmmm... Just yesterday Apple approved one of my apps built with iTGB 1.1 so it must have worked on 3.0. I don't think I'm going to target 3.0 until all the kinks are worked out. Hopefully apps built on 2.2.1 will continue to work without issue on 3.0. Still, 3.0 has several sweet features for games so I hope iTGB 1.3 comes along soon and is in a quality state.
#9
iTGB runs on 3.0 beta 5. I built it with Xcode 3.1.2 (the non-beta), targetting 2.2.1.
There are many "interesting" messages in the debugger, but the shooter runs. Making our own games should work just as usual.
05/08/2009 (9:14 pm)
90 minutes of certificate hell later, and I finally managed to get Xcode to compile again.iTGB runs on 3.0 beta 5. I built it with Xcode 3.1.2 (the non-beta), targetting 2.2.1.
There are many "interesting" messages in the debugger, but the shooter runs. Making our own games should work just as usual.
#10
05/08/2009 (9:31 pm)
Great news Ronny. Looks like you beat me to the initial testing. Feel free to post full results and tests or shoot me an e-mail directly. Just might include you in some beta testing for 1.3
#11
Obviously you should still test on OS 3.0, but you still do so with the proven 2.2.1 SDK, etc.
05/09/2009 (2:34 am)
I think that people are confusing "running on OS 3.0" with "using the 3.0 SDK". as of now, you don' t need to submit your games to Apple built for the 3.0 SDK. You only have to have your app able to run on the 3.0 OS, which unless you are doing somethung funny iand I a guessing that 99 percent of the iTGE users out there are *not*), your app should run just fine. Obviously you should still test on OS 3.0, but you still do so with the proven 2.2.1 SDK, etc.
#12
Note that beta 1-4 said 3.1.3 beta or pre-release, while this version has been named with a non-beta version. I suspect this means that Xcode itself is ready, while only the APIs and extra tools are in flux. The number of API changes in this beta is pretty small, the rest bugfixes. Their schedule has been every other Tuesday so far (I think), which means we might get a beta 6, then the public can start firing up iTunes.
I'm giving the beta SDK a test later, since it looks like we're going to have to get used to it anyway :)
P.S.:If you have an iPod touch, not an iPhone, the beta OS seems far less risky.
05/09/2009 (10:08 am)
Yep, the OS 3.0 *SDK* (Xcode 3.1.3) has issues. I think that is where GG should focus their attention, as we're now dangerously close to the real release.Note that beta 1-4 said 3.1.3 beta or pre-release, while this version has been named with a non-beta version. I suspect this means that Xcode itself is ready, while only the APIs and extra tools are in flux. The number of API changes in this beta is pretty small, the rest bugfixes. Their schedule has been every other Tuesday so far (I think), which means we might get a beta 6, then the public can start firing up iTunes.
I'm giving the beta SDK a test later, since it looks like we're going to have to get used to it anyway :)
P.S.:If you have an iPod touch, not an iPhone, the beta OS seems far less risky.
#13
3.0 SDK is being installed in about an hour or so.
05/09/2009 (10:12 am)
No turning back. I just installed the new iTunes and 3.0 OS. Running some games now, then backing everything up.3.0 SDK is being installed in about an hour or so.
#14
A tip: Inside the SDK installer, there is a package in the Packages directory for 3.0 OS development. You need to install that to the default SDK (3.1.2) also, or else Xcode won't build to a 3.0 device. You can also link the beta directory from "Platforms/iPhoneOS.platform/DeviceSupport/3.0 (7A312g)/" to the same place in /Developer.
05/09/2009 (10:20 am)
Living on the edge, Michael :)A tip: Inside the SDK installer, there is a package in the Packages directory for 3.0 OS development. You need to install that to the default SDK (3.1.2) also, or else Xcode won't build to a 3.0 device. You can also link the beta directory from "Platforms/iPhoneOS.platform/DeviceSupport/3.0 (7A312g)/" to the same place in /Developer.
#15
05/09/2009 (10:25 am)
@Ronny - Thanks for the heads up.
#16
05/09/2009 (11:27 am)
Starting the full installation...I don't think I've flinched like this while continuing an installation since Windows 98 =/
#17
05/09/2009 (11:42 am)
Xcode is five times as large as Win98. Don't you just love computers?
#18
05/09/2009 (11:45 am)
First build complete. Only 343 errors. Not a bad start.
#19
In consoleObject.h, line 274:
Was:
Removed the extra qualifier and now:
05/09/2009 (11:58 am)
Down to 88. Error was extra qualification for a class method.In consoleObject.h, line 274:
Was:
static AbstractClassRep* AbstractClassRep::findClassRep(const char* in_pClassName);
Removed the extra qualifier and now:
static AbstractClassRep* findClassRep(const char* in_pClassName);
#20
Error:../../source/persistence/tinyxml.h:879: error: extra qualification 'TiXmlDeclaration::' on member 'TiXmlDeclaration'
Original Code:
Fixed Code:
Based on some Googling, and I could be wrong, a lot of this has to do with using GCC 4.0. At any rate. Down to 83 errors.
05/09/2009 (12:02 pm)
In tinyxml.h, line 877:Error:../../source/persistence/tinyxml.h:879: error: extra qualification 'TiXmlDeclaration::' on member 'TiXmlDeclaration'
Original Code:
TiXmlDeclaration::TiXmlDeclaration( const char * _version, const char * _encoding, const char * _standalone );
Fixed Code:
TiXmlDeclaration( const char * _version, const char * _encoding, const char * _standalone );
Based on some Googling, and I could be wrong, a lot of this has to do with using GCC 4.0. At any rate. Down to 83 errors.
Torque 3D Owner Ronny Bangsund
Torque Cheerleaders