"could not load" exception using AGSLocalTiledLayer and TPK

303
2
07-10-2012 09:29 AM
EvanKirkwood
New Contributor II
Our app uses an AGSLocalTiledLayer to provide offline access to map data using a tile package (TPK). We're using v2.3 of the iOS SDK. Recently we've been encountering an exception using when the map is positioned to a certain area at certain zoom levels. This is getting logged to debug output:

2012-07-10 11:15:53.610 app[11990:19a03] could not locate: v101/Layers/_alllayers/L19/R36280C4e400.bundle
2012-07-10 11:15:53.648 app[11990:19a03] could not locate: v101/Layers/_alllayers/L19/R36280C4e400.bundlx


Looking at the contents of the TPK (by changing the extension to .zip and uncompressing it), the .bundle and .bundlx files from the debug output are indeed not there. This seems to only occur with tiles in the 2 lowest scales (L18 and L19), almost as though the tiles at those scales in the TPK were not completely generated.

So ... two questions:

  1. Has anyone encountered an issues with a TPK like this before, and if so, did you find a way to ensure all the expected tiles get included in the TPK? Any errors/warnings we ought to be looking for in ArcGIS Desktop?

  2. Is there a recommended/supported way to handle this situation when using the iOS SDK?

Here is a stack trace from a crash report when this exception is encountered:
Thread 14 Crashed:
0   libsystem_kernel.dylib         0x30d8632c __pthread_kill + 8
1   libsystem_c.dylib              0x33317208 pthread_kill + 48
2   libsystem_c.dylib              0x33310316 __abort + 86
3   libsystem_c.dylib              0x332f1b42 __chk_fail + 38
4   libsystem_c.dylib              0x332f1b0e __memcpy_chk + 6
5   app                         0x00118dcc -[AGSIndexRec readFileStream:recordSize:] (AGSIndexRec.m:39)
6   app                         0x00116c12 -[AGSVFileIndex readIndex:] (AGSVFileIndex.mm:262)
7   app                         0x00116640 -[AGSVFileIndex filePosition:] (AGSVFileIndex.mm:142)
8   app                         0x0011a098 -[AGSVFileReader readRecord:buffer:length:] (AGSVFileReader.mm:225)
9   app                         0x0011827e -[AGSVFileTileReader getTileForLOD:row:col:tileData:] (AGSVFileTileReader.m:76)
10  app                         0x0011d792 -[AGSLocalTileRequestOperation main] (AGSLocalTileRequestOperation.m:91)
11  Foundation                     0x372d138c -[__NSOperationInternal start] + 856
12  Foundation                     0x3733a78c __block_global_6 + 96
13  libdispatch.dylib              0x34a4dc52 _dispatch_call_block_and_release + 6
14  libdispatch.dylib              0x34a50810 _dispatch_worker_thread2 + 252
15  libsystem_c.dylib              0x332d2df4 _pthread_wqthread + 288
16  libsystem_c.dylib              0x332d2cc8 start_wqthread + 0
0 Kudos
2 Replies
DiveshGoyal
Esri Regular Contributor
Hi, Kirk -

Does your app crash when the exception is encountered? Or does it just log those messages in the console and continue to work (although without the tiles) ?

Can you share your TPK with us so that we can debug it.

Have you tried recreating the TPK to see if the missing files are included subsequently? What version of ArcGIS did you use to create the TPK? 10.1 Pre-release or Final?
0 Kudos
EvanKirkwood
New Contributor II
Hi, Kirk -

Does your app crash when the exception is encountered? Or does it just log those messages in the console and continue to work (although without the tiles) ?

Can you share your TPK with us so that we can debug it.

Have you tried recreating the TPK to see if the missing files are included subsequently? What version of ArcGIS did you use to create the TPK? 10.1 Pre-release or Final?


Yes, the app crashes when the exception is encountered (see crash report in the OP).

Unfortunately the TPK we're encountering the issue with contains proprietary customer information, so we can't share it.

We have tried recreating the TPK, and now suspect we may have an issue with the custom tiling schema we're using. We are currently using the pre-release version of ArcGIS 10.1 - is it possible that could be related to the TPK issues we're observing? We ran into another error - "Invalid function argument" - trying to create a TPK in NAD83 Alberta 3TM 114W projection (this is perhaps more appropriate to post in the ArcGIS Desktop forum, but any advice here would be appreciated).

Thanks,
Evan
0 Kudos