BluesZhang / gdata-objectivec-client

Automatically exported from code.google.com/p/gdata-objectivec-client
Other
0 stars 0 forks source link

iPhone crash #65

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Please delete (ignore) issue 64.  Not sure why I cannot reply to it (using 
Firefox, page is throwing errors on PC and Mac).

Released app crashes.  Cannot reproduce this error in development environment.  
Reported by Apple, and also by a user in an app that made it into the store.

Error occurs at app launch/initialization.

Crash Report:

Hardware Model:      iPod2,1
Process:         iSpiritGuide [749]
Path:            
/var/mobile/Applications/BCB19552-F9F8-4005-A910-9FF60E8487AE/iSpiritGuide.app/i
SpiritGuide
Identifier:      iSpiritGuide
Version:         ??? (???)
Code Type:       ARM (Native)
Parent Process:  launchd [1]

Date/Time:       2010-07-15 14:47:27.215 -0700
OS Version:      iPhone OS 4.0 (8A293)
Report Version:  104

Exception Type:  EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes: 0x00000001, 0x00000000
Crashed Thread:  0

Thread 0 Crashed:
0   iSpiritGuide                      0x000e5e70 GDataCreateStaticDictionary + 
40
1   iSpiritGuide                      0x000e6026 +[GDataObject load] + 2
2   libobjc.A.dylib                   0x00002b3c call_load_methods + 124
3   libobjc.A.dylib                   0x000028f0 load_images + 84
4   dyld                              0x2fe03c60 
dyld::notifySingle(dyld_image_states, ImageLoader const*) + 60
5   dyld                              0x2fe0a0ba 
ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned 
int, ImageLoader::InitializerTimingList&) + 222
6   dyld                              0x2fe0a524 
ImageLoader::runInitializers(ImageLoader::LinkContext const&, 
ImageLoader::InitializerTimingList&) + 36
7   dyld                              0x2fe022fa 
dyld::initializeMainExecutable() + 374
8   dyld                              0x2fe06d24 dyld::_main(macho_header 
const*, unsigned long, int, char const**, char const**, char const**) + 1680
9   dyld                              0x2fe01764 
dyldbootstrap::start(macho_header const*, int, char const**, long, macho_header 
const*) + 480
10  dyld                              0x2fe01058 _dyld_start + 48

Original issue reported on code.google.com by Peter.O...@gmail.com on 16 Jul 2010 at 4:38

GoogleCodeExporter commented 9 years ago
New info from my programmer:  he had been "precompiling" this library and 
including it.  When he "fresh compiled" the source code from this library for 
each individual app, the problem went away.  It is slower, but we think it will 
works.

This does not address whatever the real problem is, but hopefully it will keep 
someone from pulling an all-nighter to get apps released.

Original comment by Peter.O...@gmail.com on 17 Jul 2010 at 4:00

GoogleCodeExporter commented 9 years ago
Thanks for the new information.

It sounds like an inconsistent set of build settings between the library and 
the apps.

Original comment by gregrobbins on 17 Jul 2010 at 5:37

GoogleCodeExporter commented 9 years ago
I had one user with the same issue.  I am changing build settings now and 
resubmitting to Apple.  I will post back when I find out if it works for the 
user.

Original comment by des...@gmail.com on 17 Jul 2010 at 5:40

GoogleCodeExporter commented 9 years ago
I found a solution in my case.
Open GData.xcodeproj file.
then set "Info >> Build >> Architectures >> Standard (armv6 armv7)" 
and rebuild your project.

Original comment by allt...@gmail.com on 20 Jul 2010 at 9:26

GoogleCodeExporter commented 9 years ago
This does seem to solve the problem. My programmer figured out the release 
build and the dev build are (or at least were) different for this project.  
Thus unless it is changed by the user, they are likely to encounter the same 
issue:  testing/development will be fine, but the released app will fail.

Original comment by Peter.O...@gmail.com on 20 Jul 2010 at 10:18

GoogleCodeExporter commented 9 years ago
Worked for me as well.  I just matched BaseSDK and deployment target settings 
for all projects involved and it seems to work so far.

Original comment by des...@gmail.com on 20 Jul 2010 at 10:26