CoreData崩溃错误Xcode 11 Beta,IOS 13 Beta [英] CoreData crash error Xcode 11 Beta, IOS 13 Beta

查看:454
本文介绍了CoreData崩溃错误Xcode 11 Beta,IOS 13 Beta的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在尝试在手机IOS 13 Beta上从Xcode11 beta构建我的应用程序。加载应用程序时发生崩溃。


2019-07-22 13:58:12.910460 + 0300 GoodWine [3738:792501] [错误]错误:
一个或此应用程序中的更多模型正在使用可变形的
属性,其变压器名未设置或设置为
NSKeyedUnarchiveFromDataTransformerName。请改用
NSSecureUnarchiveFromData或
NSSecureUnarchiveFromDataTransformer的子类。在某些时候,当指定$ n
时,Core Data
将默认使用 NSSecureUnarchiveFromData,并且包含不
不支持NSSecureCoding的类的可转换属性将变得不可读。



CoreData:错误:此应用程序中的一个或多个模型使用的
可转换属性的转换器名称未设置,
或设置为NSKeyedUnarchiveFromDataTransformerName。请改用 NSSecureUnarchiveFromData或
NSSecureUnarchiveFromDataTransformer的子类切换至
。在某些时候,当指定$ n
时,Core Data
将默认使用 NSSecureUnarchiveFromData,并且包含不
不支持NSSecureCoding的类的可转换属性将变得不可读。



2019-07-22 13:58:12.910595 + 0300 GoodWine [3738:792501] [错误]
CoreData:此应用程序中的一个或多个模型正在使用
可变形的转换器名称未设置,
或设置为NSKeyedUnarchiveFromDataTransformerName的属性。请改用 NSSecureUnarchiveFromData或
NSSecureUnarchiveFromDataTransformer的子类切换至
。在某些时候,当指定$ n
时,Core Data
将默认使用 NSSecureUnarchiveFromData,并且包含不
不支持NSSecureCoding的类的可转换属性将变得不可读。



CoreData:警告:实体'SFMCKeyValueEntity'上的属性'value'是
,使用nil或不安全的NSValueTransformer。请改用
NSSecureUnarchiveFromData或
NSSecureUnarchiveFromDataTransformer的子类。



解决方案

我找到了这个解决方案。错误已消失,并且似乎可以正常工作。我一直在测试。


对于所有Transformable属性,我在数据模型检查器面板中将 Transformer设置为 NSSecureUnarchiveFromData。



编辑:


经过几天的测试,我向以前的解决方案中添加了一些内容。 / p>

如果更改后删除了该应用程序,则可以使用先前的解决方案。否则,数据模型将无法识别并从头创建,从而丢失所有历史信息(在生产中这是不可接受的!!!)。


我采用的最终解决方案是将这些更改添加到新模型中(遵循此链接)并实施迁移(始终在链接中描述)。


在这种情况下,仅显示警告更新后一次,然后消失。


Im trying building my application from Xcode11 beta on phone IOS 13 Beta. I have crash when application loading.

2019-07-22 13:58:12.910460+0300 GoodWine[3738:792501] [error] fault: One or more models in this application are using transformable properties with transformer names that are either unset, or set to NSKeyedUnarchiveFromDataTransformerName. Please switch to using "NSSecureUnarchiveFromData" or a subclass of NSSecureUnarchiveFromDataTransformer instead. At some point, Core Data will default to using "NSSecureUnarchiveFromData" when nil is specified, and transformable properties containing classes that do not support NSSecureCoding will become unreadable.

CoreData: fault: One or more models in this application are using transformable properties with transformer names that are either unset, or set to NSKeyedUnarchiveFromDataTransformerName. Please switch to using "NSSecureUnarchiveFromData" or a subclass of NSSecureUnarchiveFromDataTransformer instead. At some point, Core Data will default to using "NSSecureUnarchiveFromData" when nil is specified, and transformable properties containing classes that do not support NSSecureCoding will become unreadable.

2019-07-22 13:58:12.910595+0300 GoodWine[3738:792501] [error] CoreData: One or more models in this application are using transformable properties with transformer names that are either unset, or set to NSKeyedUnarchiveFromDataTransformerName. Please switch to using "NSSecureUnarchiveFromData" or a subclass of NSSecureUnarchiveFromDataTransformer instead. At some point, Core Data will default to using "NSSecureUnarchiveFromData" when nil is specified, and transformable properties containing classes that do not support NSSecureCoding will become unreadable.

CoreData: warning: Property 'value' on Entity 'SFMCKeyValueEntity' is using nil or an insecure NSValueTransformer. Please switch to using "NSSecureUnarchiveFromData" or a subclass of NSSecureUnarchiveFromDataTransformer instead.

解决方案

I found this solution. The errors have disappeared and it would seem to work. I keep testing.

For all Transformable attributes, I have set "Transformer" to "NSSecureUnarchiveFromData" in the Data Model Inspector panel.

EDIT:

After a few days of testing I add something to my previous solution.

The previous solution works if, after the changes, the application is deleted. Otherwise, the data model is not recognized and is created from scratch, losing all the historical information (and in production this is not acceptable!!!).

The final solution I adopted was to add these changes to a new model (following this link) and implementing the migration (always described in the link).

In this case the warning appears only once after the update and then disappears.

这篇关于CoreData崩溃错误Xcode 11 Beta,IOS 13 Beta的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆