AGSRuntimeSDKforIOS(ESri) 10.2.2 License issue, iTunes App is crashing.

3963
6
04-15-2015 07:31 AM
PritiBose
New Contributor II

https://developers.arcgis.com/ios/objective-c/guide/license-your-app.htm

I have generated ClientID as per instruction mentioned in above link, also added code in -Init

NSError *error; NSString* clientID = @"2ayVKEYIRokuuyTo"; [AGSRuntimeEnvironment setClientID:clientID error:&error]; if(error){ // We had a problem using our client ID NSLog(@"Error using client ID : %@",error); }

Watermark is vanished. i can test GIS module in my iPad App also all features are accessible. i had added above code to get rid of watermark "Licensed for developer use only".

after i upload my App, when it was approved i download from iTunes but GIS modules start Crashing...

it does not give any issue when i am debugging/testing all features like Legend, my Location ETC works properly. but App on iTunes is crashing....

any one having idea what i am missing....

Tags (3)
0 Kudos
6 Replies
GagandeepSingh
Occasional Contributor II

Hi Supriya Bhosle​,

It will be helpful if you can share the crash logs.

Gagan

0 Kudos
PritiBose
New Contributor II

Hello,

sorry i can not provide, as APP crashing which was uploaded on iTUNES, not when i develop or debug or test.

how can i get crash log of the APP i download from App store. is there any way?

Esri has added License from 10.2.2 if i am not wrong, we always used AGSRunTimeSDKforIOS 10.1.1 and there was no issue. this license issue is coming up after i upgraded SDK to 10.2.2.

where exactly below code i have to used

NSError *error; NSString* clientID = @"2ayVKEYIRokuuyTo";[AGSRuntimeEnvironment setClientID:clientID error:&error]; if(error){ // We had a problem using our client ID NSLog(@"Error using client ID : %@",error); }

is it only once or every time when i access GIS feature? i have separate GIS module, so i had added in - (id) init

but every time when ever i access GIS feature - (id) init of UIViewControllers get called, but throughs error as Error using client ID :  but while development/ debugging/testing we can access all GIS feature without any issue. so i upload APP on iTunes, but when i check uploaded APP it started crashing.

0 Kudos
GagandeepSingh
Occasional Contributor II

Technical Q&A QA1747: Debugging Deployed iOS Apps

Getting Crash Logs and Console Output With Xcode

Even though you won't be able to run the app in Xcode's debugger, Xcode can still give you all the information you need to debug the problem.

Using Xcode 6

1) Plug in the device and open Xcode

2) Choose Window -> Devices from the Xcode menu

3) Under the DEVICES section in the left column, choose the device

4) To see crash logs, select the View Device Logs button under the Device Information section on the right hand panel

5) To see the device console, click the up-triangle at the bottom left of the right hand panel to show the device console, then click the down arrow on the bottom right to save the console as a file

6) Find your app in the Process column and select the Crash log to see the contents.

7) Xcode 6 will also list low memory logs here; these will be shown with a Process name "Unknown" and Type "Unknown. You can examine the contents of the log to determine whether any of these are caused by your app. For more information about low memory logs, see Understanding and Analyzing iOS Application Crash Reports.

Using Xcode 5

1) Plug in the device and open Xcode

2) Open the Organizer window and select the Devices tab

3) Under the DEVICES section in the left column, expand the listing for the device

4) Select Device Logs to see crash logs or select Console to see Console output

PritiBose
New Contributor II

Thread 13:

0   libsystem_kernel.dylib         0x312799cc __workq_kernreturn + 8

1   libsystem_pthread.dylib       0x312f3ea8 _pthread_wqthread + 788

2   libsystem_pthread.dylib       0x312f3b80 start_wqthread + 4

Thread 0 crashed with ARM Thread State (32-bit):

    r0: 0x0128eda8    r1: 0x26c9ca5b      r2: 0x2325c5d8      r3: 0x00000000

    r4: 0x00000000    r5: 0x2325c5d8      r6: 0x0128eda8      r7: 0x0128dc5c

    r8: 0x315621c8    r9: 0x00000000     r10: 0x010059dc     r11: 0x315621c8

    ip: 0x00000000    sp: 0x0128dc48      lr: 0x23d4cda9      pc: 0x30c3ef56

  cpsr: 0x60000030

Binary Images:

0x31000 - 0xf00fff  armv7  <a4795163616a32b1b346e83323a9f3f5> /var/mobile/Containers/Bundle/Application/8A43FFE5-5B02-4B90-BA38-CC815B862262/

0x1fecc000 - 0x1feeffff dyld armv7s  <7216b86d38393128b0da3b7109d30710> /usr/lib/dyld

0x219b4000 - 0x21ac8fff IMGSGX554GLDriver armv7s  <001824a951ef3fc388b555a7df6772fc> /System/Library/Extensions/IMGSGX554GLDriver.bundle/IMGSGX554GLDriver

0x21ad4000 - 0x21c40fff AVFoundation armv7s  <23a20af23f733b39b5c87059c080f9f7> /System/Library/Frameworks/AVFoundation.framework/AVFoundation

BLA.....BLA.......BLA........

i am getting this crash only for GIS modules rest all modules are working fine, sometime GIS module will open but inside even if i click on any feature like Legend APP crash..... is it some setting issue with SDK (i am using AGSRunTimeSDK10.2.2)

0 Kudos
GagandeepSingh
Occasional Contributor II

From the part of the crash log you posted, it seems like the problem is with the AVFoundation.framework and not the GIS module.

0 Kudos
PritiBose
New Contributor II

Hello,

its actually very big LOG i did post only starting lines , but in that case my entire apps should be crashing right, while only GIS modules, we have almost 6-7 modules all are working fine except GIS.

in betw. i also tried to run app in release mode.... i did not got total GIS crash as in App store APP. but some time APP did crash on GIS, with similar log. specially Polygon. but it did not repet next time.

what is your suggestion, i tried to search on net but i did not get proper reason as such........

i did upload app working app in Feb with IOS 6.1 as base SDK with AGSRunTimeSDK 10.1.1. was working fine all this while, what i change is upgraded base SDK to IOS 7 and AGSRunTimeSDK 10.2.2 (valid architecture : arm64 armv7), support for arm64.

main point is it crash only for GIS...

0 Kudos