{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 走好不送 的问题《Why am I getting a CoreData error in my iOS or OSX》','https://www.manongdao.com/q-926470.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
I get the following error during a build.
"API Misuse: Attempt to serialize store access on non-owning coordinator (PSC = 0x7fb5ae208890, store PSC = 0x0) CoreData
Why am I getting a CoreData error in my app? I'm not using CoreData!
相关问题
- Core Data lightweight migration crashes after App
- How can I implement password recovery in an iPhone
- Authentication Failure using Git-LFS Azure DevOps
- State preservation and restoration strategies with
- “Zero out” sensitive String data in Swift
相关文章
- 现在使用swift开发ios应用好还是swift？
- UITableView dragging distance with UIRefreshContro
- TCC __TCCAccessRequest_block_invoke
- Where does a host app handle NSExtensionContext#co
- Swift - hide pickerView after value selected
- How do you detect key up / key down events from a
- didBeginContact:(SKPhysicsContact *)contact not in
- Attempt to present UIAlertController on View Contr
This message is not referring to your use of CoreData, rather it is referring to Xcode's internal use in order to manage part of your project.
One possibility (it happened to me) is that there is corruption in one of the .xcassets files in your project.
In my case a problem with git-lfs meant that the .xcasset file did not have contents. Correcting this (in my case with a git-lfs pull) meant that once the assets within the .xcassets file were available, the compilation error was fixed.
So in general check .xcassets files and any other Xcode managed project resources that might require use of CoreData internally to XCode