SAP Knowledge Base Article - Preview

2569438 - An iOS app crashes in a method of the Cache class with error message: Thread x: EXC_BAD_ACCESS (code=1, address=<addressValue>)

Symptom

An iOS application crashes when it calls a method of the OData SDKs Cache class with the below error message:

Thread x: EXC_BAD_ACCESS (code=1, address=<addressValue>)


Read more...

Environment

  • SAP Mobile Platform (SMP) SDK 3.0
  • Apple iOS

Product

SAP Mobile Platform SDK 3.0

Keywords

Thread x: EXC_BAD_ACCESS (code=1, address=<addressValue>), cache, cache.h, object, memory, allocation, pointer, dereference, dereferencing, address, thread, thread-safety, initializeCacheWithError:, - readEntriesForUrlKey:withError:, readEntriesLocalForEntryId:forEntityType:withError:, mergeEntriesFromFeed:forUrlKey:withError:withCompletionBlock:, mergeEntries:forUrlKey:withError:withCompletionBlock:, addEntry:withError:, updateEntry:withError:, deleteEntryForEntryId:withError:, clearCacheForUrlKey:withError:, clearLocalEntryForEntryId:withError:, getDeltaLinkForUrlKey:withError:, storeDocument:forDocType:forUrlKey:withError:, readDocumentForUrlKey:forDocType:withError:, addNotificationDelegate:withListener:forUrlKey:, isPersistable, urlkey, error, issue, ns, ios, apple, sdk, api, odata, online, serial queue, GCD , KBA , MOB-SDK-ODP , SAP Mobile SDK Odata SDK , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.