Feedback Hermes IOS

[joaodematejr]

Description

I created a new application and installed it but it doesn't open the application, some Flipper log, Create a CRUD

Stacktrace & log output

https://user-images.githubusercontent.com/17418041/132082412-f4b181a4-94f4-4143-9baf-127ca935de2f.png

https://user-images.githubusercontent.com/17418041/132082402-35ef247b-8458-4b69-83ee-acd0ffa2a9b0.png

https://user-images.githubusercontent.com/17418041/132082139-859b4b21-d6af-4fc7-b946-f49f216ac0aa.png

https://user-images.githubusercontent.com/17418041/132082034-668758fa-9120-4d51-ab86-80a17174de92.png

Process: realmHermes [16230]
Path: /Users/USER/Library/Developer/CoreSimulator/Devices/A0FFE31C-C19D-4CAC-917B-010B6CE3F4A2/data/Containers/Bundle/Application/732FAEC5-5CE9-4101-B41A-59C0DC19BF48/realmHermes.app/realmHermes
Identifier: realmHermes
Version: 1.0 (1)
Code Type: X86-64 (Native)
Parent Process: launchd_sim [11811]
Responsible: SimulatorTrampoline [7116]
User ID: 501

Date/Time: 2021-09-04 01:10:10.191 -0300
OS Version: macOS 11.5.2 (20G95)
Report Version: 12
Anonymous UUID: 1E47EC22-9B28-370B-4B8C-FC36E91171B3

Time Awake Since Boot: 5600 seconds

System Integrity Protection: disabled

Crashed Thread: 12 com.facebook.react.JavaScript

Exception Type: EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes: 0x0000000000000001, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Illegal instruction: 4
Termination Reason: Namespace SIGNAL, Code 0x4
Terminating Process: exc handler [16230]

Application Specific Information:
CoreSimulator 757.5 - Device: iPhone 8 (A0FFE31C-C19D-4CAC-917B-010B6CE3F4A2) - Runtime: iOS 14.5 (18E182) - DeviceType: iPhone 8

Thread 0:: Dispatch queue: com.apple.main-thread
0 com.apple.CoreFoundation 0x00007fff2038b171 __CFRunLoopRun + 2789
1 com.apple.CoreFoundation 0x00007fff2038a1a7 CFRunLoopRunSpecific + 567
2 com.apple.GraphicsServices 0x00007fff2b874d85 GSEventRunModal + 139
3 com.apple.UIKitCore 0x00007fff246c14df -[UIApplication _run] + 912
4 com.apple.UIKitCore 0x00007fff246c639c UIApplicationMain + 101
5 org.reactjs.native.example.realmHermes 0x000000010ed664d0 main + 112 (main.m:7)
6 libdyld.dylib 0x00007fff2025abbd start + 1

EXC_BAD_INSTRUCTION

EXC_BAD_INSTRUCTION

Process: realmHermes [21541]
Path: /Users/USER/Library/Developer/CoreSimulator/Devices/D5A0AFC6-F590-4E42-8B9D-867AD36CB43A/data/Containers/Bundle/Application/6AF8443A-4B97-4CCE-86AC-9F90A66740CA/realmHermes.app/realmHermes
Identifier: realmHermes
Version: 1.0 (1)
Code Type: X86-64 (Native)
Parent Process: launchd_sim [18331]
Responsible: SimulatorTrampoline [7116]
User ID: 501

Date/Time: 2021-09-04 01:27:10.133 -0300
OS Version: macOS 11.5.2 (20G95)
Report Version: 12
Anonymous UUID: 1E47EC22-9B28-370B-4B8C-FC36E91171B3

Time Awake Since Boot: 6600 seconds

System Integrity Protection: disabled

Crashed Thread: 12 com.facebook.react.JavaScript

Exception Type: EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes: 0x0000000000000001, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Illegal instruction: 4
Termination Reason: Namespace SIGNAL, Code 0x4
Terminating Process: exc handler [21541]

Application Specific Information:
CoreSimulator 757.5 - Device: iPhone 12 (D5A0AFC6-F590-4E42-8B9D-867AD36CB43A) - Runtime: iOS 14.5 (18E182) - DeviceType: iPhone 12

Thread 0:: Dispatch queue: com.apple.main-thread
0 com.apple.CFNetwork 0x00007fff237203e4 0x7fff2353f000 + 1971172
1 com.apple.CoreFoundation 0x00007fff20392513 _CFRelease + 244
2 com.apple.CFNetwork 0x00007fff235ed2a9 0x7fff2353f000 + 713385
3 libobjc.A.dylib 0x00007fff20178c42 object_cxxDestructFromClass(objc_object*, objc_class*) + 83
4 libobjc.A.dylib 0x00007fff2018abee objc_destructInstance + 64
5 libobjc.A.dylib 0x00007fff20190d88 -[NSObject dealloc] + 21
6 com.apple.CFNetwork 0x00007fff236fff51 0x7fff2353f000 + 1838929
7 libobjc.A.dylib 0x00007fff20191604 objc_object::sidetable_release(bool, bool) + 174
8 com.apple.CFNetwork 0x00007fff237017c5 0x7fff2353f000 + 1845189
9 libobjc.A.dylib 0x00007fff20191604 objc_object::sidetable_release(bool, bool) + 174
10 com.apple.CFNetwork 0x00007fff2377bddb 0x7fff2353f000 + 2346459
11 com.apple.CFNetwork 0x00007fff23556f4f 0x7fff2353f000 + 98127
12 libobjc.A.dylib 0x00007fff20191604 objc_object::sidetable_release(bool, bool) + 174
13 libobjc.A.dylib 0x00007fff20192dc7 AutoreleasePoolPage::releaseUntil(objc_object**) + 175
14 libobjc.A.dylib 0x00007fff20192cb6 objc_autoreleasePoolPop + 185
15 com.apple.CoreFoundation 0x00007fff20432036 _CFAutoreleasePoolPop + 22
16 com.apple.CoreFoundation 0x00007fff2038fd5c __CFRunLoopPerCalloutARPEnd + 41
17 com.apple.CoreFoundation 0x00007fff2038b1a2 __CFRunLoopRun + 2838
18 com.apple.CoreFoundation 0x00007fff2038a1a7 CFRunLoopRunSpecific + 567
19 com.apple.GraphicsServices 0x00007fff2b874d85 GSEventRunModal + 139
20 com.apple.UIKitCore 0x00007fff246c14df -[UIApplication _run] + 912
21 com.apple.UIKitCore 0x00007fff246c639c UIApplicationMain + 101
22 org.reactjs.native.example.realmHermes 0x0000000109f3e4d0 main + 112 (main.m:7)
23 libdyld.dylib 0x00007fff2025abbd start + 1

Can you reproduce a bug?

Yes, always

Reproduction Steps

I created a new project using the latest version of RN and installed it using npm then accessed the IOS folder and ran the pod install command and started the project.

https://github.com/joaodematejr/realmHermes

Version

10.20.0-alpha.0

What SDK flavour are you using?

Local Database only

Are you using encryption?

No response

Platform OS and version(s)

platform :ios, '11.0'

[takameyer]

@joaodematejr thanks for reporting. As Hermes support is still under development. We will track this issue and report when it has been resolved.

[joaodematejr]

@takameyer As soon as you have a new update please let me know if possible to perform new tests. Thanks

[fronck]

@joaodematejr At the moment, we require React Native 0.66.0-rc3 for our experimental Hermes support (see #3940). According to your package.json, you are using version 0.65.1.

Please upgrade your React Native framework and let us know if the problem persists.

[no-response]

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.