Home › Forums › Ask the Flomies › x86_64 architecture missing?
Tagged: PRO SDK
-
AuthorPosts
-
April 29, 2019 at 6:06 pm #65186
Hello
I’m getting
FlomioSDKPro.framework/FlomioSDKPro, missing required architecture x86_64 in file ...
on the Pro SDK.The free one worked. How do I fix this? This is on XCode 10.2.1.
April 29, 2019 at 6:56 pm #65211Hi Nicolai, we don’t offer simulator support (x86) for the Flomio SDK (basic or otherwise) because it’s a challenging thing to support across the Apple ecosystem.
best,
RichardApril 30, 2019 at 5:09 am #65239Hey
This thread was one of my posts that never surfaced (until now). Did you find the forum error perhaps? 🙂 This is why I asked the question “twice”. I didn’t mean to be annoying.
Anyway; what this means is that I can’t use the SDK because it breaks my use of Storyboards, as they are built using the same architecture as the simulator. Any IBDesignables then don’t work and my project is riddled with Auto-Layout issues. I’ve confirmed that removing Flomio immediately fixes this issue: In practice this means I’ll have to comment out every use/mention/import of the SDK to build and work on my app. It isn’t really a viable solution in the long run, as this NFC reader thing is only a minor feature of our platform and not something I’m willing to bother development with this much.
I obviously don’t know what the exact issue is, but you don’t need it to work on the simulator, it just needs to be able to build on the x86_64 architecture to fix this.
May 2, 2019 at 6:31 am #65259Hi Nicolai,
I have updated the Pro link you received with a ‘fat’ release of the FlomioSDKPro Framework.
Hopefully this fixes your issues.
Scott
May 2, 2019 at 7:28 am #65260Hello Scott
I downloaded the SDK, and it does build and run now, but the Interface builder now crashes when the SDK is included. I tried every trick known to man; clear DerivedData, rebuild, restart XCode and so on to no avail. Removing the Framework immediately resolves the issue.
I have the log for the IBDesignables crash, as that’s the only output I receive. I don’t know if it helps you narrow down the problem. It seems like it’s a EXC_BAD_ACCESS error, but other than that I don’t know.
Process: IBDesignablesAgent-iOS [12918] Path: /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/Library/Xcode/Overlays/IBDesignablesAgent-iOS Identifier: IBDesignablesAgent-iOS Version: 10.2.1 (14490.49) Code Type: X86-64 (Native) Parent Process: launchd_sim [10468] Responsible: IBDesignablesAgent-iOS [12918] User ID: 501 Date/Time: 2019-05-02 13:20:42.152 +0200 OS Version: Mac OS X 10.14.4 (18E226) Report Version: 12 Bridge OS Version: 3.0 (14Y677) Anonymous UUID: 82D496BD-F235-5B41-EFE7-0771602F90BA Sleep/Wake UUID: A43B59F6-EA2D-44B3-8193-EA74D22AB204 Time Awake Since Boot: 600000 seconds Time Since Wake: 1800 seconds System Integrity Protection: enabled Crashed Thread: 0 Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: EXC_I386_GPFLT Exception Note: EXC_CORPSE_NOTIFY Termination Signal: Segmentation fault: 11 Termination Reason: Namespace SIGNAL, Code 0xb Terminating Process: exc handler [12918] Application Specific Information: CoreSimulator 587.35 - Device: iPad Pro (9.7-inch) (8FC977F8-F3F1-4D7E-9EE7-57789E99A7F2) - Runtime: iOS 12.2 (16E226) - DeviceType: iPad Pro (9.7-inch) Thread 0 Crashed: 0 libobjc.A.dylib 0x000000010793799b objc_release + 11 1 com.apple.CoreFoundation 0x0000000108f16e56 _CFAutoreleasePoolPop + 22 2 com.apple.CoreFoundation 0x0000000108e59f5e __CFRunLoopRun + 2318 3 com.apple.CoreFoundation 0x0000000108e59302 CFRunLoopRunSpecific + 626 4 com.apple.Foundation 0x00000001073f0044 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 277 5 com.apple.dt.IBFoundation 0x0000000106ef928b -[IBAbstractPlatformTool startServingReceiveChannel:] + 446 6 com.apple.dt.IBFoundation 0x0000000106ef94fd -[IBAbstractPlatformTool startServingWriteDescriptor:readDescriptor:] + 119 7 com.apple.dt.IBFoundation 0x0000000106efa38d +[IBAbstractPlatformTool main] + 1209 8 IBDesignablesAgent-iOS 0x0000000105b82957 main + 34 9 libdyld.dylib 0x000000010f42d541 start + 1 Thread 1: 0 com.apple.CoreFoundation 0x0000000108eaccb0 CFStringConvertNSStringEncodingToEncoding + 0 1 com.apple.Foundation 0x0000000107402f42 -[NSString(NSStringOtherEncodings) getBytes:maxLength:usedLength:encoding:options:range:remainingRange:] + 50 2 com.apple.Foundation 0x00000001073e500e _NS_os_log_callback + 356 3 libsystem_trace.dylib 0x000000010f6b8c42 _os_log_fmt_flatten_NSCF + 42 4 libsystem_trace.dylib 0x000000010f6b7f5e _os_log_fmt_flatten_data + 202 5 libsystem_trace.dylib 0x000000010f6be621 _os_log_impl_flatten_and_send + 1779 6 libsystem_trace.dylib 0x000000010f6bdf0f _os_log_error_impl + 113 7 com.apple.CoreFoundation 0x0000000108f7f642 CFBundleCopyLocalizedStringForLocalization + 1794 8 com.apple.CFNetwork 0x00000001096ec7fc _CFNetworkErrorMapErrorCode(long, __CFString const*, __CFString const*, __CFString const*, __CFString const*, __CFString const*, __CFString const*, __CFString const*, __CFString const*) + 85 9 com.apple.CFNetwork 0x00000001096ec693 _CFNetworkErrorInitLocalizedStringsDictionary() + 1767 10 libsystem_pthread.dylib 0x000000010f7a0ce3 __pthread_once_handler + 65 11 libsystem_platform.dylib 0x000000010f78eacb _os_once_callout + 18 12 libsystem_pthread.dylib 0x000000010f7a0c7f pthread_once + 56 13 com.apple.CFNetwork 0x00000001096eaf8b _CFNetworkErrorGetLocalizedString(long, long) + 39 14 com.apple.CFNetwork 0x00000001096eb036 _CFNetworkErrorCopyLocalizedDescriptionWithHostname + 73 15 com.apple.Foundation 0x00000001074334cc localizedDescriptionForError + 55 16 com.apple.Foundation 0x0000000107433726 -[NSError(NSURLExtrasInternal) _web_initWithDomain_nowarn:code:URL:] + 174 17 com.apple.Foundation 0x00000001074332c5 +[NSError(NSURLExtras) _web_errorWithDomain:code:URL:] + 59 18 com.apple.CFNetwork 0x000000010964e8e1 -[__NSCFLocalSessionTask _onqueue_cancel] + 27 19 libdispatch.dylib 0x000000010f3beccf _dispatch_call_block_and_release + 12 20 libdispatch.dylib 0x000000010f3bfd02 _dispatch_client_callout + 8 21 libdispatch.dylib 0x000000010f3c6720 _dispatch_lane_serial_drain + 705 22 libdispatch.dylib 0x000000010f3c7261 _dispatch_lane_invoke + 398 23 libdispatch.dylib 0x000000010f3cffcb _dispatch_workloop_worker_thread + 645 24 libsystem_pthread.dylib 0x000000010f7a1611 _pthread_wqthread + 421 25 libsystem_pthread.dylib 0x000000010f7a13fd start_wqthread + 13 Thread 2: 0 libsystem_kernel.dylib 0x000000010f74cef2 read + 10 1 com.apple.Foundation 0x0000000107374ea1 -[NSConcreteFileHandle readDataOfLength:] + 449 2 com.apple.dt.IBFoundation 0x0000000106ef90b2 -[IBAbstractPlatformTool _WAIT_FOR_PARENT_TO_EXIT:] + 30 3 com.apple.dt.IBFoundation 0x0000000106ef93d9 __53-[IBAbstractPlatformTool startServingReceiveChannel:]_block_invoke_2 + 28 4 libdispatch.dylib 0x000000010f3beccf _dispatch_call_block_and_release + 12 5 libdispatch.dylib 0x000000010f3bfd02 _dispatch_client_callout + 8 6 libdispatch.dylib 0x000000010f3c26be _dispatch_continuation_pop + 440 7 libdispatch.dylib 0x000000010f3c1d49 _dispatch_async_redirect_invoke + 817 8 libdispatch.dylib 0x000000010f3cead3 _dispatch_root_queue_drain + 355 9 libdispatch.dylib 0x000000010f3cf330 _dispatch_worker_thread2 + 97 10 libsystem_pthread.dylib 0x000000010f7a16b3 _pthread_wqthread + 583 11 libsystem_pthread.dylib 0x000000010f7a13fd start_wqthread + 13 Thread 3: 0 libsystem_kernel.dylib 0x000000010f76a02e readv + 10 1 com.apple.dt.IBFoundation 0x0000000106f3c95f -[IBMessageReceiveChannel runBlockingReceiveLoopNotifyingQueue:notifyingTarget:context:] + 1185 2 com.apple.dt.IBFoundation 0x0000000106ef8e9c -[IBAbstractPlatformTool runMessageChannel:] + 87 3 com.apple.Foundation 0x0000000107405307 __NSThread__start__ + 1197 4 libsystem_pthread.dylib 0x000000010f7a22eb _pthread_body + 126 5 libsystem_pthread.dylib 0x000000010f7a5249 _pthread_start + 66 6 libsystem_pthread.dylib 0x000000010f7a140d thread_start + 13 Thread 4: 0 libsystem_pthread.dylib 0x000000010f7a13f0 start_wqthread + 0 Thread 0 crashed with X86 Thread State (64-bit): rax: 0x5000000000000000 rbx: 0x00007fa04e81b010 rcx: 0x00007fa04e81b878 rdx: 0x0000000000000303 rdi: 0x00007fa04dc01330 rsi: 0x0000000000000303 rbp: 0x00007ffeea07c530 rsp: 0x00007ffeea07c0f8 r8: 0x0000000000000003 r9: 0x00007fa04dcb9f40 r10: 0x0000000000000004 r11: 0x0000000000000004 r12: 0xa3a3a3a3a3a3a3a3 r13: 0x00007fa04fb04500 r14: 0x00007fa04e81b818 r15: 0x00007fa04e81b000 rip: 0x000000010793799b rfl: 0x0000000000010206 cr2: 0x0000000106e4c185 Logical CPU: 4 Error Code: 0x00000000 Trap Number: 13
May 2, 2019 at 7:49 am #65261Ok, have you made sure you’ve done the configuration steps in https://docs.flomio.com/#configure-project-settings
?Make sure it’s linked in your Embedded Binaries, and that when you drag the sdk in you click “copy items if needed”
These issues are always annoying to debug. Also, check if it still works with the old sdk you had.
May 2, 2019 at 7:52 am #65262Yes, I’ve done that. It works on the simulator; it boots up the app and runs just fine, but it just crashes Interface Builder in Storyboards, so my custom views don’t render. I don’t really understand why as it should be the same architecture in storyboards as in sim, and there is nothing interface-related in the SDK anyway. Pretty weird :/
May 2, 2019 at 9:00 am #65270Yeah, that is pretty weird.
Any idea how I could replicate so I can try help with the debugging?So I understand your issue correctly, when you are editing your custom view in Interface Builder, the app crashes?
May 2, 2019 at 9:06 am #65271I suppose you could do this:
1. Make sure you have XCode 10.2.1
2. Implement a custom view that implements IBDesignables. Guide here for convenience: https://blog.supereasyapps.com/how-to-create-round-buttons-using-ibdesignable-on-ios-11/
3. Once you verify your custom view works in storyboard, try importing the FlomioSDK you sent me and see if you can still use your views inside storyboards.See this link for the exact error I encounter: https://i.ibb.co/ccFV3Vw/Screenshot-2019-05-02-at-15-01-48.png
Edit: So no, nothing crashes the app. The app works, but storyboards don’t. The IBDesignable agent crashes and as a result the custom views are not displayed.
May 2, 2019 at 9:47 am #65272Thanks for the steps to debug. We’re very low on bandwidth at the moment, if you could provide a project to replicate the issue that would be great. Otherwise this will be addressed at a later date but we cannot prioritize it at the moment.
You are welcome to purchase Flomio Service Hours if this is business critical and you would like it addressed immediately.
Scott
- This reply was modified 5 years, 7 months ago by Scott.
May 2, 2019 at 11:37 am #65274Hey Scott
I’ve created a project that suffers from this error. As the Pro Framework is embedded I best not post it publicly. Where can I send it?
May 15, 2019 at 10:26 am #65332I’m going to bump this, Scott.
Where do you want me to send the demo project that doesn’t work?
May 28, 2019 at 5:18 pm #65390Nicolai, please email the project bundle to info@flomio.com and we’ll try to reproduce.
best,
Richard -
AuthorPosts
You must be logged in to reply to this topic.