企业发行版在Swift App中与iOS8不相称

前端之家收集整理的这篇文章主要介绍了企业发行版在Swift App中与iOS8不相称前端之家小编觉得挺不错的,现在分享给大家,也给大家做个参考。
我在使用我的 swift应用程序在iOS 8设备上运行Enterprise构建时遇到问题.如果我使用非企业帐户进行代码签名,它似乎工作正常.有人遇到过这个问题吗?

以下是尝试使用企业帐户运行构建时在iOS设备上获取的崩溃日志:

OS Version: iOS 8.0 (12A4345d) Report Version: 105

Exception Type: EXC_BREAKPOINT (SIGTRAP) Exception Codes:
0x0000000000000001,0x00000001200d5088 Triggered by Thread: 0

OS Version: iOS 8.0 (12A4345d) Report Version: 105

Exception Type: EXC_BREAKPOINT (SIGTRAP) Exception Codes:
0x0000000000000001,0x00000001200d5088 Triggered by Thread: 0

Dyld Error Message: Library not loaded: @rpath/libswiftCore.dylib
Referenced from:
/private/var/mobile/Containers/Bundle/Application/EFD559CA-9D7C-481D-9CA5-BF0B8EB6A3F5/Beta.app/Beta
Reason: no suitable image found. Did find:
/private/var/mobile/Containers/Bundle/Application/EFD559CA-9D7C-481D-9CA5-BF0B8EB6A3F5/Riva
Beta.app/Frameworks/libswiftCore.dylib: mmap() error 1 at
address=0x100478000,size=0x00194000 segment=__TEXT in Segment::map()
mapping
/private/var/mobile/Containers/Bundle/Application/EFD559CA-9D7C-481D-9CA5-BF0B8EB6A3F5/Beta.app/Frameworks/libswiftCore.dylib
Dyld Version: 353.5

Binary Images: 0x1200d4000 – 0x1200fbfff dyld arm64
/usr/lib/dyld 0x182b58000 –
0x182b58fff Accelerate arm64
/System/Library/Frameworks/Accelerate.framework/Accelerate 0x18436c000
– 0x1844cefff CoreGraphics arm64 <60c80ae53baf35cabcb3e09d2a454b55> /System/Library/Frameworks/CoreGraphics.framework/CoreGraphics
0x184b08000 – 0x184b78fff CoreTelephony arm64
<2e0d3b51a01330e7a8a08a05a25dfa12>
/System/Library/Frameworks/CoreTelephony.framework/CoreTelephony
0x184f70000 – 0x1851c4fff Foundation arm64
<473783d2bf1a3ceb969a4a863831eba4>
/System/Library/Frameworks/Foundation.framework/Foundation 0x185344000
– 0x1855defff ImageIO arm64 /System/Library/Frameworks/ImageIO.framework/ImageIO 0x186a5c000 –
0x186b2ffff MessageUI arm64 <3ddc5ee0fd4e36a3bee79ed61ec5d705>
/System/Library/Frameworks/MessageUI.framework/MessageUI 0x186ba4000 –
0x186c53fff MobileCoreServices arm64

/System/Library/Frameworks/MobileCoreServices.framework/MobileCoreServices
0x1880b4000 – 0x188238fff QuartzCore arm64

/System/Library/Frameworks/QuartzCore.framework/QuartzCore 0x1884cc000
– 0x18851dfff Security arm64 <8436c45c606d3d28b2938904dbf0b206> /System/Library/Frameworks/Security.framework/Security 0x1886e4000 –
0x188757fff SystemConfiguration arm64

/System/Library/Frameworks/SystemConfiguration.framework/SystemConfiguration
0x18875c000 – 0x1890b8fff UIKit arm64
<3989dfad77f33a8ea10e009f0dba82a3>
/System/Library/Frameworks/UIKit.framework/UIKit 0x194488000 –
0x194559fff libsqlite3.dylib arm64
/usr/lib/libsqlite3.dylib

所有这些都在本文中详细解释:

https://www.airsignapp.com/ios-apps-using-swift-crash-when-signed-with-inhouse-certificate/

We can confirm that after create a new cert and
.mobileprovision,no more issues.

We found origins that caused this issue,related to a missing attribute in
“Subject” field InHouse Certificates :

BEFORE Subject: UID=269J2W3P2L,
CN=iPhone Distribution: Company Name,O=Company Name,C=FR

AFTER Subject: UID=269J2W3P2L,CN=iPhone Distribution: Company Name,
OU=269J2W3P2L,C=FR

原文链接:https://www.f2er.com/swift/319118.html

猜你在找的Swift相关文章