Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.

iOS 4.3 App Rejected

Discussion in 'iOS and tvOS' started by glenwn, Mar 24, 2011.

  1. glenwn

    glenwn

    Joined:
    Feb 20, 2009
    Posts:
    18
    My app has been rejected twice because it crashed at launch. I’ve tested the app on both iPhone 4, iPhone 3Gs and an iPod Touch 1st gen. It runs flawlessly and doesn’t crash at any time.

    My problem is that I cannot reproduce the crash, so how can I fix it?

    The crash report from Apple states:

    Code (csharp):
    1. Incident Identifier: 11CE3AA7-D0DA-47B6-AB69-8FD7978B53DF
    2. CrashReporter Key:   6c65ebc370405a56c5c88207e8f50fda869ae6c7
    3. Hardware Model:      iPhone3,1
    4. Process:         timbersaxe [2494]
    5. Path:            /var/mobile/Applications/47FC94D6-322E-419D-97B7-7AA5ADD08DE0/timbersaxe.app/timbersaxe
    6. Identifier:      timbersaxe
    7. Version:         ??? (???)
    8. Code Type:       ARM (Native)
    9. Parent Process:  launchd [1]
    10.  
    11. Date/Time:       2011-03-23 14:33:21.845 -0700
    12. OS Version:      iPhone OS 4.3 (8F190)
    13. Report Version:  104
    14.  
    15. Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
    16. Exception Codes: KERN_INVALID_ADDRESS at 0xf33558e3
    17. Crashed Thread:  0
    18.  
    19. Thread 0 name:  Dispatch queue: com.apple.main-thread
    20. Thread 0 Crashed:
    21. 0   timbersaxe                      0x0079f5b8 0x1000 + 7988664
    22. 1   timbersaxe                      0x006bf20c 0x1000 + 7070220
    23. 2   timbersaxe                      0x0039ca0c 0x1000 + 3783180
    24. 3   timbersaxe                      0x00003fa8 0x1000 + 12200
    25. 4   timbersaxe                      0x0000295c 0x1000 + 6492
    26.  
    27. Thread 0 crashed with ARM Thread State:
    28.     r0: 0x0d02bf3e    r1: 0x27307b61      r2: 0x34333a9f      r3: 0x00000000
    29.     r4: 0xf33558e3    r5: 0x001796d3      r6: 0x00a57580      r7: 0x2fdffa50
    30.     r8: 0x0079eb80    r9: 0x00000001     r10: 0x340afcf8     r11: 0x00000000
    31.     ip: 0x00000001    sp: 0x2fdffa2c      lr: 0xffffffff      pc: 0x0079f5b8
    32.   cpsr: 0xa0000010
    Any suggestions?

    I’ve submitted a game a month ago running iOS 4.2 which got approved right away. Could this be an issue related to iOS 4.3?

    Thanks
     
  2. scinfu

    scinfu

    Joined:
    Oct 23, 2008
    Posts:
    404
    your game work on IOS 4.3 ?

    there is some problem with Unity and 4.3 ...
     
  3. glenwn

    glenwn

    Joined:
    Feb 20, 2009
    Posts:
    18
    Yes, it works perfectly. The first time I make a build there are thousands of warnings. If I build again all the warnings are gone. I have tried installing the game on about six different devices and it runs without any problems, but it crashes instantly on the review team's phones.
     
  4. Crazy Robot

    Crazy Robot

    Joined:
    Apr 18, 2009
    Posts:
    921
    You may have to wait until Unity supports 4.3, there maybe something you can't see.
     
  5. glenwn

    glenwn

    Joined:
    Feb 20, 2009
    Posts:
    18
    Yeah. I'll guess you are right. I just have to be patient :)

    I'm not an expert in crash report, but something tells me that "Crashed Thread: 0" is something that are way out off my hands.

    Thanks for your quick replies anyway :)
     
  6. francksitbon

    francksitbon

    Joined:
    Jan 22, 2010
    Posts:
    268
    Hi do you have an EXec bad access when running with last version of Xcode ? (crash when launched by xcode, but then run with no bug if launch from device)

    See this thread for more info : http://forum.unity3d.com/threads/80573-iOS-4.3
     
  7. danielsonchris

    danielsonchris

    Joined:
    Feb 12, 2011
    Posts:
    43
    What version of Unity are you running?
     
  8. danielsonchris

    danielsonchris

    Joined:
    Feb 12, 2011
    Posts:
    43
    Just as an additional note. It looks like Apple just released a new version of XCode 4.0.1 yesterday. That may or may not help anything...
     
  9. synapsemassage

    synapsemassage

    Joined:
    Jul 27, 2009
    Posts:
    334
    I also experienced problems that are maybe related to yours. During development I always used to build with script call optimisations "slow and save" (player settings) and everything was running without any problems on every device but for release builds I switched to "fast and no exceptions" that gave me some EXC_BAD_ACCESS. EXC_BAD_ACCESS means usually that something is missing or cannot be found like empty variable/gameobject. Checking for this I found a script that missed an object. Weird that this wasn't catched earlier by the debugger.
     
  10. francksitbon

    francksitbon

    Joined:
    Jan 22, 2010
    Posts:
    268
    Is there any strong fps enhancement using fast but no exception in stead of slow and safe ?
     
  11. glenwn

    glenwn

    Joined:
    Feb 20, 2009
    Posts:
    18
    Downgraded to iOS 4.2 and it got approved right away.

    @francksitbon My experience tells me that there are little fps enhancement using fast but no exceptions.
     
  12. sealiongames

    sealiongames

    Joined:
    Oct 6, 2008
    Posts:
    98
    @glenwn - interesting workaround downgrading to 4.2 SDK - I thought it was a submission requirement to build with the current version of the SDK.

    I'm using SDK 4.3 with XCode 3. Just for comparison, when you were building with SDK 4.3 were you using XCode 3.x or XCode 4.x? -Thanks!
     
    Last edited: Mar 28, 2011
  13. minevr

    minevr

    Joined:
    Mar 4, 2008
    Posts:
    1,017
    Me too....EXC_BAD_ACCESS (SIGBUS)
     
  14. minevr

    minevr

    Joined:
    Mar 4, 2008
    Posts:
    1,017
    Binary Uploaded Mar 26, 2011 11:17 AM
    2.1: Apps that crash will be rejected
    Mar 27, 2011 09:50 PM. From Apple.
    2.1

    We found that your app crashed on iPhone 4 and iPad running iOS 4.3.1, which is not in compliance with the App Store Review Guidelines.

    Your app crashed on launch.

    We have attached detailed crash logs to help troubleshoot this issue. For information on how to read a crash log, please see Tech Note TN2151 Understanding and Analyzing iPhone OS Application Crash Reports: <https://developer.apple.com/library/ios/#technotes/tn2008/tn2151.html>.

    For discrete code-level questions, you may wish to consult with Apple Developer Technical Support at <http://developer.apple.com/support/resources/technicalsupport/>. Depending on your questions, be sure to include any symbolicated crash logs, screenshots, or steps to reproduce the issues you’ve encountered.
     
  15. glenwn

    glenwn

    Joined:
    Feb 20, 2009
    Posts:
    18
    @sealiongames I've tried building for iOS 4.3 in both Xcode 3 and 4 with no luck using any of them. The app got rejected with the same error log on both of them.
     
  16. minevr

    minevr

    Joined:
    Mar 4, 2008
    Posts:
    1,017
    I think uesed base sdk 4.2 build it,that's ok!
     
  17. Mantas-Puida

    Mantas-Puida

    Unity Technologies

    Joined:
    Nov 13, 2008
    Posts:
    1,864
    Hi,
    are you using any of third party libraries? There have been cases when using thumb-compiled third party libraries were causing random crashes. If you aren't using such library please submit a bugreport with repro case attached to it.
    Thanks!
     
  18. Mantas-Puida

    Mantas-Puida

    Unity Technologies

    Joined:
    Nov 13, 2008
    Posts:
    1,864
    Unity 3.3 supports iOS SDK 4.3 (with Xcode 3.x) not worse than iOS SDK 4.2 (when setting iOS SDK version to "iOS latest" in Player Settings).

    All the trouble reports for iOS SDK 4.3, which we received, were not caused by the iOS SDK version change. Top reasons for failures were (usually reported as EXC_BAD_ACCESS in Xcode):
    - Using third party thumb-compiled libs (which are not supported by Unity).
    - Using features that are not supported on iOS platform, like Terrain. (There is known issue with Unity Editor, which allows you to build project with unsupported features).
    - User script problems, where scripts access uninitialized variables.

    If you have problems other than mentioned above please report a bug with repro case attached to it.
    Thanks!
     
  19. designxtek

    designxtek

    Joined:
    Mar 13, 2009
    Posts:
    147
    apple rejected my build using iOS SDK 4.3 with Xcode 4.

    I built the application again on iOS SDK 4.2 with Xcode 3.x and it got approved right away.

    Something is wrong with Unity3D and iOS SDK 4.3 w/ Xcode 4
     
  20. Mantas-Puida

    Mantas-Puida

    Unity Technologies

    Joined:
    Nov 13, 2008
    Posts:
    1,864
    Please report a bug!
    Thanks
     
  21. Tudor_n

    Tudor_n

    Joined:
    Dec 10, 2009
    Posts:
    359
    Oddly enough, things are looking completely different here. Doing anything heavily touch-related using "Slow but Safe" is snail-like slow.
     
  22. maxfax2009

    maxfax2009

    Joined:
    Feb 4, 2009
    Posts:
    410
    Hi

    Using Unity 3.3 and Xcode 4.0.1 and iOS SDK 4.3

    Exception Type: EXC_BAD_ACCESS (SIGBUS)
    Exception Codes: KERN_PROTECTION_FAILURE at 0x00000000
    Crashed Thread: 0


    I used "Fast but no exceptions" and "use micro mscorlib" :(
     
  23. Jehu

    Jehu

    Joined:
    Aug 19, 2010
    Posts:
    16
    Yep - Apple rejected mine also with iOS SDK 4.3 with Xcode 4 - even though I tested it on iPhone 4, iPhone 3 and iPod Touch.

    EXC_BAD_ACCESS again

    So I am going to try designtek's suggestion of building with iOS SDK 4.2 with Xcode 3.x
     
  24. maxfax2009

    maxfax2009

    Joined:
    Feb 4, 2009
    Posts:
    410
    can you submit using iOS SDK 4.2?

    I don't see then download anymore
     
  25. Deleted User

    Deleted User

    Guest

    Same here, I submitted a minor HyperBowl update using XCode 4 with only a couple of changes from the version I submitted with XCode 3, and got similar crash reports on submission. Runs fine on my test devices, including an iPad running iOS 4.3.1. ARM6+7, iPhone+iPad, stripped, fast with no exceptions, also using the Prime31 GameCenter plugin.

    I'm not looking forward to redownloading all 4GB of Xcode 3, plus it won't recognize my updated iPad now ( maxfax2009 - the XCode 3 download link is visible on the iOS Dev Center page if you log into the developer program first)
     
  26. Dreamora

    Dreamora

    Joined:
    Apr 5, 2008
    Posts:
    26,601
    technicat: thats wrong

    Even the iOS 4.2 SDK recognizes 4.3.1 devices

    Apple has learnt from their past errors and reworked the way devices are authorized, its no longer os based but xcode extracts data from the device, sends them to apple for verification and gets its answer from there. (takes 2-5mins)
     
  27. Deleted User

    Deleted User

    Guest

    Hm, I thought XCode was complaining about 4.3 on my devices until I upgraded to XCode 4, but I may be misremembering. Nevertheless, I'll probably wait until this XCode 4 issue is sorted out (I just downloaded XCode 4.0.1 today but haven't tried it out). My home office is using the Android 2.2 mobile hotspot feature on my phone, so I really have to plan out my big downloads (and uploads).
     
  28. Dreamora

    Dreamora

    Joined:
    Apr 5, 2008
    Posts:
    26,601
    Perhaps you were on the 4.1 or 4.0 SDK.
    or you missinterpreted the message cause when you update the os on the device you need to go into xcode - organizer and activate the device again.
     
  29. maxfax2009

    maxfax2009

    Joined:
    Feb 4, 2009
    Posts:
    410
    I tested it with Xcode 3.2.6 and SDK 4.3.1 and it still crashing!!!!

    OS Version: iPhone OS 4.3.1 (8G4)
    Report Version: 104

    Exception Type: EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes: KERN_INVALID_ADDRESS at 0x0a50c584
    Crashed Thread: 0
     
  30. Mantas-Puida

    Mantas-Puida

    Unity Technologies

    Joined:
    Nov 13, 2008
    Posts:
    1,864
    Please check Unity Manual iOS troubleshooting page (http://unity3d.com/support/documentation/Manual/TroubleShooting.html#iPhoneTroubleShooting) and try to obtain stack trace. Without stack trace it is quite impossible to help you.
     
  31. maxfax2009

    maxfax2009

    Joined:
    Feb 4, 2009
    Posts:
    410
    @Mantasp

    It does not crash on my system and the debug as no EXC_BAD_ACCESS , it only as this once Apple tests it.


    you mean the crash log from Apple:

    Exception Type: EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes: KERN_INVALID_ADDRESS at 0x0a50c584
    Crashed Thread: 0

    Thread 0 name: Dispatch queue: com.apple.main-thread
    Thread 0 Crashed:
    0 AstroDash 0x013b101c 0x1000 + 20643868
    1 AstroDash 0x012d0c7c 0x1000 + 19725436
    2 AstroDash 0x00f3f478 0x1000 + 15983736
    3 AstroDash 0x00004564 0x1000 + 13668
    4 AstroDash 0x00003000 0x1000 + 8192

    Thread 0 crashed with ARM Thread State:
    r0: 0x82943161 r1: 0xd6d074ac r2: 0x82943161 r3: 0x00000000
    r4: 0x0157baec r5: 0x001cc8eb r6: 0x01632e10 r7: 0x2fdffa58
    r8: 0x013b05f0 r9: 0x00000000 r10: 0x00000000 r11: 0x00000000
    ip: 0x00000000 sp: 0x2fdffa34 lr: 0xffffffff pc: 0x013b101c
    cpsr: 0x80000010
     
    Last edited: Apr 1, 2011
  32. Mantas-Puida

    Mantas-Puida

    Unity Technologies

    Joined:
    Nov 13, 2008
    Posts:
    1,864
    When you have crash report from Apple you can try to symbolicate (resolve symbolic names for stack frames). There are several advices how to do this: http://stackoverflow.com/questions/1460892/symbolicating-iphone-app-crash-reports
     
  33. maxfax2009

    maxfax2009

    Joined:
    Feb 4, 2009
    Posts:
    410
    0 AstroDash 0x013b101c FMOD::SystemI::createChannelGroupInternal(char const*, FMOD::ChannelGroupI**, bool, bool) + 2349388
    1 AstroDash 0x012d0c7c FMOD::SystemI::createChannelGroupInternal(char const*, FMOD::ChannelGroupI**, bool, bool) + 1430956
    2 AstroDash 0x00f3f478 start + 15975576
    3 AstroDash 0x00004564 start + 5508
    4 AstroDash 0x00003000 start + 32


    Is not FMOD the sound in Unity ?
     
  34. sealiongames

    sealiongames

    Joined:
    Oct 6, 2008
    Posts:
    98
    @maxfax2009 or @glenwn - Here's a guess based on a previous experience- does your unity app built with sdk 4.3 crash on your system at app start up when running with Pandora playing music as a background task?
     
    Last edited: Apr 1, 2011
  35. synapsemassage

    synapsemassage

    Joined:
    Jul 27, 2009
    Posts:
    334
    System? Debug? Apple rejected your App already? Or what do you mean with that? Did you submit your build with "fast and exceptions" or "slow and safe"? Did you test your App with "fast and exceptions" before submitting to Appstore or only tested with "slow and safe"? Some EXC_BAD_ACCESS only happen when building with "fast and no exceptions". Check this! I also had instantly crashing game when building with "fast and no exceptions", there was a problem with a variable only showing up in "fast and noc exception"!
     
  36. Mantas-Puida

    Mantas-Puida

    Unity Technologies

    Joined:
    Nov 13, 2008
    Posts:
    1,864
    Ok that's not good. We always see such stack trace when symbols are stripped from release build. Please submit your release Xcode project and Apple's crash reports as bug. PM me your bug number and I will to extract something more useful.
     
  37. minevr

    minevr

    Joined:
    Mar 4, 2008
    Posts:
    1,017
    xcode Version 3.2.6,base sdk : ios4.2,

    On:iphone3g,itouch2,iphone4(4.2os),iphone4(4.3.1os)
    I can't find crash.

    but,apple "2.1: Apps that crash will be rejected"

    How to fixed it....sigh~~~
     
  38. minevr

    minevr

    Joined:
    Mar 4, 2008
    Posts:
    1,017
    I send a error report....
     
  39. FIllbiker

    FIllbiker

    Joined:
    Jun 9, 2010
    Posts:
    118
    It is realy strange...there are many new apps that crashes in Appstore, but our games, that we tested on many devices, many FWs and with no crashes, are rejected. :(
     
  40. minevr

    minevr

    Joined:
    Mar 4, 2008
    Posts:
    1,017
    Apple Feedback: starts, flash, exit.

    Our tests are normal. can not see the crash.

    ipad1,iphone3g,iphone3gs,iphone4,itouch4,itouch2


    Anger!!
     
  41. minevr

    minevr

    Joined:
    Mar 4, 2008
    Posts:
    1,017
    I used xcode3 sdk4.2 or sdk4.3, is rejected..
     
  42. FiveFingers

    FiveFingers

    Joined:
    Oct 15, 2009
    Posts:
    541
    Our game update was just approved (using xcode3.x and SDK4.2) but has a weird problem in "default" orientation!

    This is crazy!!!
     
  43. francksitbon

    francksitbon

    Joined:
    Jan 22, 2010
    Posts:
    268
    Hi, about your tests: did you test the game with last version of Xcode ? Don't you have any Exec bad access errors playing the game launched through Xcode ? It is strange that if everything works fine, apple should not have a bad access..
    Each time I test my app, I test it entirely through Xcode to detect any bad access (I found a lot). But your feedback makes me fear about my future submission after 6 months of production.
     
    Last edited: Apr 2, 2011
  44. minevr

    minevr

    Joined:
    Mar 4, 2008
    Posts:
    1,017
    base sdk : 4.2.0
    Used Xcode Version 3.2.5,build is ok.

    Used Xcode Version 3.2.6,build is ok,but have 2630 warnings..

    Why?
     
  45. minevr

    minevr

    Joined:
    Mar 4, 2008
    Posts:
    1,017
    ld: warning: ARM function mono_aot_version not 4-byte aligned
    ld: warning: ARM function mono_aot_full_aot not 4-byte aligned
    ld: warning: ARM function mono_runtime_version not 4-byte aligned
    ld: warning: ARM function mono_aot_assembly_name not 4-byte aligned
    ld: warning: ARM function name_0 not 4-byte aligned
    ld: warning: ARM function name_1 not 4-byte aligned
    ld: warning: ARM function name_2 not 4-byte aligned
    ld: warning: ARM function name_3 not 4-byte aligned
    ld: warning: ARM function name_4 not 4-byte aligned
    ld: warning: ARM function name_5 not 4-byte aligned
    ld: warning: ARM function name_6 not 4-byte aligned
    ld: warning: ARM function name_7 not 4-byte aligned
    ld: warning: ARM function name_9 not 4-byte aligned
    ld: warning: ARM function name_10 not 4-byte aligned
    ld: warning: ARM function name_11 not 4-byte aligned
    ld: warning: ARM function name_13 not 4-byte aligned
    ld: warning: ARM function name_14 not 4-byte aligned
    ld: warning: ARM function name_15 not 4-byte aligned
    ld: warning: ARM function name_16 not 4-byte aligned
    ld: warning: ARM function name_18 not 4-byte aligned
    ld: warning: ARM function name_19 not 4-byte aligned
    ld: warning: ARM function name_20 not 4-byte aligned
    ld: warning: ARM function name_22 not 4-byte aligned
    ld: warning: ARM function name_23 not 4-byte aligned
    ld: warning: ARM function name_25 not 4-byte aligned
    ld: warning: ARM function name_27 not 4-byte aligned
    ld: warning: ARM function name_28 not 4-byte aligned
    ld: warning: ARM function mono_aot_version not 4-byte aligned
    ld: warning: ARM function mono_aot_full_aot not 4-byte aligned
    ld: warning: ARM function mono_runtime_version not 4-byte aligned
    ld: warning: ARM function mono_aot_assembly_name not 4-byte aligned
    ld: warning: ARM function name_0 not 4-byte aligned
    ld: warning: ARM function name_1 not 4-byte aligned
    ld: warning: ARM function name_2 not 4-byte aligned
    ld: warning: ARM function name_3 not 4-byte aligned
    ld: warning: ARM function name_4 not 4-byte aligned
    ld: warning: ARM function name_5 not 4-byte aligned
    ld: warning: ARM function name_6 not 4-byte aligned
    ld: warning: ARM function name_7 not 4-byte aligned
    ld: warning: ARM function name_9 not 4-byte aligned
    ld: warning: ARM function name_10 not 4-byte aligned
    ld: warning: ARM function name_11 not 4-byte aligned
    ld: warning: ARM function name_13 not 4-byte aligned
    ld: warning: ARM function name_14 not 4-byte aligned
    ld: warning: ARM function name_15 not 4-byte aligned
    ld: warning: ARM function name_16 not 4-byte aligned
    ld: warning: ARM function name_18 not 4-byte aligned
    ld: warning: ARM function name_19 not 4-byte aligned
    ld: warning: ARM function name_20 not 4-byte aligned
    ld: warning: ARM function name_22 not 4-byte aligned
    ld: warning: ARM function name_23 not 4-byte aligned
    ld: warning: ARM function name_25 not 4-byte aligned
    ld: warning: ARM function name_27 not 4-byte aligned
    ld: warning: ARM function name_28 not 4-byte aligned
    ld: warning: ARM function mono_aot_version not 4-byte aligned
    ld: warning: ARM function mono_aot_full_aot not 4-byte aligned
    ld: warning: ARM function mono_runtime_version not 4-byte aligned
    ld: warning: ARM function mono_aot_assembly_name not 4-byte aligned
    ld: warning: ARM function name_0 not 4-byte aligned
    ld: warning: ARM function name_1 not 4-byte aligned
    ld: warning: ARM function name_2 not 4-byte aligned
    ld: warning: ARM function name_4 not 4-byte aligned
    ld: warning: ARM function name_5 not 4-byte aligned
    ld: warning: ARM function name_6 not 4-byte aligned
    ld: warning: ARM function name_8 not 4-byte aligned
    ld: warning: ARM function name_9 not 4-byte aligned
    ld: warning: ARM function name_10 not 4-byte aligned
    ld: warning: ARM function name_12 not 4-byte aligned
    ld: warning: ARM function name_13 not 4-byte aligned
    ld: warning: ARM function name_14 not 4-byte aligned
    ld: warning: ARM function name_16 not 4-byte aligned
    ld: warning: ARM function name_17 not 4-byte aligned
    ld: warning: ARM function name_18 not 4-byte aligned
    ld: warning: ARM function name_19 not 4-byte aligned
    ld: warning: ARM function name_20 not 4-byte aligned
    ld: warning: ARM function name_21 not 4-byte aligned
    ld: warning: ARM function name_22 not 4-byte aligned
    ld: warning: ARM function name_23 not 4-byte aligned
    ld: warning: ARM function name_24 not 4-byte aligned
    ld: warning: ARM function name_25 not 4-byte aligned
    ld: warning: ARM function name_26 not 4-byte aligned
    ld: warning: ARM function name_27 not 4-byte aligned
    ld: warning: ARM function name_28 not 4-byte aligned
    ld: warning: ARM function name_29 not 4-byte aligned
    ld: warning: ARM function name_30 not 4-byte aligned
    ld: warning: ARM function name_31 not 4-byte aligned
    ld: warning: ARM function name_32 not 4-byte aligned
    ld: warning: ARM function name_33 not 4-byte aligned
    ld: warning: ARM function name_34 not 4-byte aligned
    ld: warning: ARM function name_35 not 4-byte aligned
    ld: warning: ARM function name_36 not 4-byte aligned
     
  46. francksitbon

    francksitbon

    Joined:
    Jan 22, 2010
    Posts:
    268
    Sorry I was talking about exec bad access errors
     
  47. Mantas-Puida

    Mantas-Puida

    Unity Technologies

    Joined:
    Nov 13, 2008
    Posts:
    1,864
    These are harmless - ignore them.
     
  48. minevr

    minevr

    Joined:
    Mar 4, 2008
    Posts:
    1,017
    I'm afraid not.
    I am using Xcode 3.2.5 Build and re-upload to App store, (Xcode is no warning). hope is ok,can't rejected.
    But the same project, the same SDK, there will be more than 2,000 warning with Xcode3.2.6. Strange....
     
    Last edited: Apr 2, 2011
  49. minevr

    minevr

    Joined:
    Mar 4, 2008
    Posts:
    1,017
    I send a mail to "Unity QA <bugs@unity3d.com>".

    Contains: crash log,my xcode project.
     
  50. Mantas-Puida

    Mantas-Puida

    Unity Technologies

    Joined:
    Nov 13, 2008
    Posts:
    1,864
    I was able to decipher crash log stack traces, but it gives almost no clue why it is crashing in Apple's environment and not crashing in yours.
    The stack traces point to the very first calls during application initialization and this code is pretty much static and essentially the same for all applications. We tried to reproduce problem locally, but we had no luck there. Application runs fine on all devices we tested (including the same iPhone 4 + iOS 4.3 as declared in Apple's crash reports).

    We will continue our effort to reproduce problem locally.
     
unityunity