Support Topics Documentation Slack YouTube Blog

iOS SDK 4.0.21 Query causes uncaught exception


(Renato N) #1

Starting in the iOS 4.0.21 SDK, the following code with my example query …


let whereClause = "Featured = true and ((Business is not null and Business.Active = true and Geo is not null) or (Location is not null and (Location.objectId in (Business[Active = true].Locations.objectId))) or (Geo is not null)) and ((Visible = true) and Time_End after \'2018-03-23T23:25:39-06:00\')"
let q = DataQueryBuilder().setWhereClause(whereClause)
Backendless.sharedInstance().data.of(Event.self).find(q, response: { (resp) in
      //use resp
}) { (fault) in
     //error
}

(I modified the example query to hard code a date value)

That causes the following uncaught exception with 4.0.21 (but works fine with 4.0.20):


2018-03-23 23:34:08.088165-0600 [48279:4268030] -[StringType getCacheKey]: unrecognized selector sent to instance 0x6080002054b0
2018-03-23 23:34:08.090580-0600 [48279:4268030] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[StringType getCacheKey]: unrecognized selector sent to instance 0x6080002054b0'
*** First throw call stack:
(
	0   CoreFoundation                      0x000000010a7471e6 __exceptionPreprocess + 294
	1   libobjc.A.dylib                     0x000000010988f031 objc_exception_throw + 48
	2   CoreFoundation                      0x000000010a7c8784 -[NSObject(NSObject) doesNotRecognizeSelector:] + 132
	3   CoreFoundation                      0x000000010a6c9898 ___forwarding___ + 1432
	4   CoreFoundation                      0x000000010a6c9278 _CF_forwarding_prep_0 + 120
	5                          0x0000000104c959b1 -[AnonymousObject setFieldsDirect:cache:] + 1282
	6                          0x0000000104c96c5d -[AnonymousObject adapt:cache:] + 1290
	7                          0x0000000104c95db0 -[AnonymousObject setFieldsDirect:cache:] + 2305
	8                          0x0000000104c96c5d -[AnonymousObject adapt:cache:] + 1290
	9                          0x0000000104c88730 -[ArrayType defaultAdapt:] + 625
	10                         0x0000000104c88b1d -[BodyHolderFactory createObject:] + 114
	11                         0x0000000104c95bed -[AnonymousObject setFieldsDirect:cache:] + 1854
	12                         0x0000000104c96c5d -[AnonymousObject adapt:cache:] + 1290
	13                         0x0000000104c96d5c -[DefaultAdapter adapt:] + 37
	14                         0x0000000104ca3a94 -[AdaptResponder responseHandler:] + 40
	15                         0x0000000104c77599 -[HttpEngine processAsyncAMFResponse:] + 453
	16  libdispatch.dylib                   0x000000010e5d6807 _dispatch_call_block_and_release + 12
	17  libdispatch.dylib                   0x000000010e5d7848 _dispatch_client_callout + 8
	18  libdispatch.dylib                   0x000000010e5e292b _dispatch_main_queue_callback_4CF + 628
	19  CoreFoundation                      0x000000010a709c99 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 9
	20  CoreFoundation                      0x000000010a6cdea6 __CFRunLoopRun + 2342
	21  CoreFoundation                      0x000000010a6cd30b CFRunLoopRunSpecific + 635
	22  GraphicsServices                    0x00000001102fea73 GSEventRunModal + 62
	23  UIKit                               0x0000000106cfd097 UIApplicationMain + 159
	24                         0x0000000104adc637 main + 55
	25  libdyld.dylib                       0x000000010e654955 start + 1
	26  ???                                 0x0000000000000001 0x0 + 1
)

App ID is A324EB2B-1BF5-EB0A-FF36-62F47D198E00


(Olga Danylova) #2

Hello Renato,

I’ve checked this issue and I can’t reproduce it - it works fine both for v.4.0.21 and 4.0.24 (I receive the array of the Event items).
Please update to the latest version of iOS and provide more info if the error occurs.

Regards, Olga


(Renato N) #3

Hi Olga, Just curious - what version of Xcode are you using? Let me see if I can do some more digging and see if it could be related to that?


(Renato N) #4

Hi again Olga,

I noticed a stack trace in slack that almost looked like my issue, and just updated to the latest pod (4.0.27), and the issue seems to be gone. Thank you, I think it’s good to close this! :slight_smile:

Renato