Add NSPrivacyAccessedAPICategoryDiskSpace to the privacy manifest #8511
Xcode Cloud / RealmSwift | osx-swift-evolution_15.3 | Test - macOS
succeeded
Mar 11, 2024 in 17m 45s
58 warnings
| Report Summary | |
|---|---|
| Errors | 0 |
| Test Failures | 0 |
| Analysis Issues | 0 |
| Warnings | 58 |
Details
58 Warnings
Details
RealmSwift/Tests/AnyRealmValueTests.swift:911
Switch covers known cases, but 'AnyRealmValue' may have additional unknown values
Passing argument of non-sendable type 'XCTestCase' outside of main actor-isolated context may introduce data races
Non-sendable type 'Realm' returned by implicitly asynchronous call to nonisolated function cannot cross actor boundary
Non-sendable type 'Realm' returned by implicitly asynchronous call to nonisolated function cannot cross actor boundary
Passing argument of non-sendable type 'XCTestCase' outside of main actor-isolated context may introduce data races
Non-sendable type 'Realm' returned by implicitly asynchronous call to nonisolated function cannot cross actor boundary
Add '@preconcurrency' to suppress 'Sendable'-related warnings from module 'RealmSwift'
Non-sendable type 'Realm' returned by implicitly asynchronous call to nonisolated function cannot cross actor boundary
Non-sendable type 'Realm' returned by implicitly asynchronous call to nonisolated function cannot cross actor boundary
Double-quoted include "RLMRealm_Private.h" in framework header, expected angle-bracketed insteadnot stripping binary because it is signed: /Volumes/workspace/DerivedData/Build/Products/Release/Realm.framework/Versions/A/Realm
Non-sendable type 'RealmPublishers.Value.Output?' (aka 'Optional') returned by implicitly asynchronous call to nonisolated function cannot cross actor boundary
Non-sendable type 'Realm' returned by implicitly asynchronous call to nonisolated function cannot cross actor boundary
Non-sendable type 'Realm' returned by implicitly asynchronous call to nonisolated function cannot cross actor boundarynot stripping binary because it is signed: /Volumes/workspace/DerivedData/Build/Products/Release/RealmSwift.framework/Versions/A/RealmSwift
Passing argument of non-sendable type 'XCTestCase' outside of main actor-isolated context may introduce data races
'16777217' is not exactly representable as 'Float'; it becomes '16777216'
Non-sendable type 'Realm' returned by implicitly asynchronous call to nonisolated function cannot cross actor boundary
Double-quoted include "RLMRealm_Private.h" in framework header, expected angle-bracketed instead
Passing argument of non-sendable type 'Realm' into actor-isolated context may introduce data races
Passing argument of non-sendable type 'XCTestCase' outside of main actor-isolated context may introduce data races
Non-sendable type 'Realm' returned by implicitly asynchronous call to nonisolated function cannot cross actor boundary
Non-sendable type 'Realm' returned by implicitly asynchronous call to nonisolated function cannot cross actor boundary
Passing argument of non-sendable type 'XCTestCase' outside of main actor-isolated context may introduce data racesNo App Category is set for target 'TestHost'. Set a category by using the General tab for your target, or by adding an appropriate LSApplicationCategory value to your Info.plist.
No newline at end of file
Add '@preconcurrency' to suppress 'Sendable'-related warnings from module 'RealmSwift'
Passing argument of non-sendable type 'XCTestCase' outside of main actor-isolated context may introduce data races
Non-sendable type 'Realm' returned by implicitly asynchronous call to nonisolated function cannot cross actor boundary
Non-sendable type 'Realm' returned by implicitly asynchronous call to nonisolated function cannot cross actor boundary
Non-sendable type 'Realm' returned by implicitly asynchronous call to nonisolated function cannot cross actor boundary
Passing argument of non-sendable type 'XCTestCase' outside of main actor-isolated context may introduce data races
Passing argument of non-sendable type 'XCTestCase' outside of main actor-isolated context may introduce data races
Non-sendable type 'Realm' returned by implicitly asynchronous call to nonisolated function cannot cross actor boundary
Passing argument of non-sendable type 'XCTestCase' outside of main actor-isolated context may introduce data races
Switch covers known cases, but 'AnyRealmValue' may have additional unknown valuesDirect access in function 'realm::sync::InstructionApplier::operator()(realm::sync::instr::SetErase const&)::SetEraseResolver::on_set(realm::SetBase&)' from file '/Volumes/workspace/DerivedData/Build/Products/Release/librealm-monorepo.a(instruction_applier.o)' to global weak symbol 'typeinfo for realm::Set' from file '/Volumes/workspace/DerivedData/Build/Products/Release/librealm-monorepo.a(set.o)' means the weak symbol cannot be overridden at runtime. This was likely caused by different translation units being compiled with different visibility settings.
Passing argument of non-sendable type 'XCTestCase' outside of main actor-isolated context may introduce data races
Passing argument of non-sendable type 'XCTestCase' outside of main actor-isolated context may introduce data races
Passing argument of non-sendable type 'XCTestCase' outside of main actor-isolated context may introduce data races
Non-sendable type 'Realm' returned by implicitly asynchronous call to nonisolated function cannot cross actor boundary
Passing argument of non-sendable type 'XCTestCase' outside of main actor-isolated context may introduce data races
Add '@preconcurrency' to suppress 'Sendable'-related warnings from module 'RealmSwift'
Passing argument of non-sendable type 'XCTestCase' outside of main actor-isolated context may introduce data races
Passing argument of non-sendable type 'XCTestCase' outside of main actor-isolated context may introduce data races
Public struct 'RealmSwift.Realm' shadows module 'Realm', which may cause failures when importing 'RealmSwift' or its clients in some configurations; please rename either the struct 'RealmSwift.Realm' or the module 'Realm', or see https://github.com/apple/swift/issues/56573 for workaroundsDirect access in function 'realm::sync::InstructionApplier::operator()(realm::sync::instr::SetInsert const&)::SetInsertResolver::on_set(realm::SetBase&)' from file '/Volumes/workspace/DerivedData/Build/Products/Release/librealm-monorepo.a(instruction_applier.o)' to global weak symbol 'typeinfo for realm::Set' from file '/Volumes/workspace/DerivedData/Build/Products/Release/librealm-monorepo.a(set.o)' means the weak symbol cannot be overridden at runtime. This was likely caused by different translation units being compiled with different visibility settings.
Passing argument of non-sendable type 'RLMRealm' outside of actor-isolated context may introduce data races
Passing argument of non-sendable type 'XCTestCase' outside of main actor-isolated context may introduce data races
Passing argument of non-sendable type 'XCTestCase' outside of main actor-isolated context may introduce data races
Passing argument of non-sendable type 'inout TaskGroup' (aka 'inout TaskGroup') outside of main actor-isolated context may introduce data races
Non-sendable type 'Realm' returned by implicitly asynchronous call to nonisolated function cannot cross actor boundary
Passing argument of non-sendable type 'XCTestCase' outside of main actor-isolated context may introduce data races
Non-sendable type 'Realm' returned by implicitly asynchronous call to nonisolated function cannot cross actor boundary
Non-sendable type 'Realm' returned by implicitly asynchronous call to nonisolated function cannot cross actor boundary
Passing argument of non-sendable type 'XCTestCase' outside of main actor-isolated context may introduce data races
Non-sendable type 'Realm' returned by implicitly asynchronous call to nonisolated function cannot cross actor boundary
Non-sendable type 'RealmPublishers.ObjectChangeset.Output?' (aka 'Optional>') returned by implicitly asynchronous call to nonisolated function cannot cross actor boundary
Loading