Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

App termination due to [NSURLResponse allHeaderFields]: unrecognized selector sent to instance #28589

Closed
kennetpostigo opened this issue Apr 10, 2020 · 6 comments
Labels
Needs: Triage 🔍 Resolution: Locked This issue was locked by the bot.

Comments

@kennetpostigo
Copy link

Description

My app basically crashes after reaching 100% from the code being bundled.
So far what I have done is:

If anyone has any idea why I get this issue below, so far I have followed linked issues point to logbox/flipper image issue. There are no useful instructions or hints on how to fix this issue and/or the issue has been closed. I've spent hours trying to figure this issue out 🥺

I'd be super glad if anyone can point me in the right direction to get this figured out:

Terminating app due to uncaught exception 'NSInvalidArgumentException', 
reason: '-[NSURLResponse allHeaderFields]: 
unrecognized selector sent to instance 0x6000002756e0'
*** First throw call stack:
(
	0   CoreFoundation                      0x00007fff23e3dcce __exceptionPreprocess + 350
	1   libobjc.A.dylib                     0x00007fff50b3b9b2 objc_exception_throw + 48
	2   CoreFoundation                      0x00007fff23e5e9f4 -[NSObject(NSObject) doesNotRecognizeSelector:] + 132
	3   CoreFoundation                      0x00007fff23e426cc ___forwarding___ + 1436
	4   CoreFoundation                      0x00007fff23e449b8 _CF_forwarding_prep_0 + 120
	5   yotie                               0x00000001091de02c +[SKResponseInfo shouldStripReponseBodyWithResponse:] + 76
	6   yotie                               0x00000001091ddf01 -[SKResponseInfo initWithIndentifier:timestamp:response:data:] + 241
	7   yotie                               0x00000001091b7cd9 __71-[FLEXNetworkRecorder recordLoadingFinishedWithRequestID:responseBody:]_block_invoke + 825
	8   libdispatch.dylib                   0x000000010cf6ff11 _dispatch_call_block_and_release + 12
	9   libdispatch.dylib                   0x000000010cf70e8e _dispatch_client_callout + 8
	10  libdispatch.dylib                   0x000000010cf776fd _dispatch_lane_serial_drain + 788
	11  libdispatch.dylib                   0x000000010cf7828f _dispatch_lane_invoke + 422
	12  libdispatch.dylib                   0x000000010cf83b65 _dispatch_workloop_worker_thread + 719
	13  libsystem_pthread.dylib             0x00007fff51b9ea3d _pthread_wqthread + 290
	14  libsystem_pthread.dylib             0x00007fff51b9db77 start_wqthread + 15
)
libc++abi.dylib: terminating with uncaught exception of type NSException
(lldb) 

React Native version:

0.62.2

Steps To Reproduce

Expected Results

App to open up and run properly

@guhungry
Copy link
Contributor

guhungry commented Apr 11, 2020

@kennetpostigo is it because of base64 image as #28583?
I have this problem too with react native 0.62.1

@kennetpostigo
Copy link
Author

@guhungry I don't even think i'm using a base64 image anywhere

@ivanmoskalev
Copy link
Contributor

Can this be related to #28454?

@kennetpostigo
Copy link
Author

Updating flipper to at least 37 fixed this

@tushar-innovalabs
Copy link

Using this post I fixed this issue: #28583 (comment) and #28583 (comment)

@azhararmar
Copy link

@Tushar-Inno it worked for me as well on RN 0.62.2, thank you.

@facebook facebook locked as resolved and limited conversation to collaborators Oct 1, 2021
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label Oct 1, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Needs: Triage 🔍 Resolution: Locked This issue was locked by the bot.
Projects
None yet
Development

No branches or pull requests

6 participants