Search results for

“SwiftData inheritance relationship”

4,982 results found

Post

Replies

Boosts

Views

Activity

error: the replacement path doesn't exist <- how bad is this error, should i care - is it important?
I get this error, i have my own DIKit, and i want to use swiftdata for showing info from persisten model. It works all over the app, but i get this error with my .sheet. // JobCreationView.swift // Features // // Created by Jens Vik on 26/03/2025. // import SwiftUI import DesignKit import DIKit import PresentationKit import CoreKit import DomainKit import SwiftData public struct JobCreationView: View { @Binding var isPresented: Bool // Inject view model using DIKit's property wrapper @Injected((any JobCreationViewModelProtocol).self) private var viewModel // Form state @Injected(ModelContext.self) private var modelContext @State private var date = Date() @State private var isASAP = false @State private var price = @State private var jobType = Fiks @State private var description = // Available job types private let jobTypes = [Fiks, Fiksit] @Query private var userContexts: [UserContextModel] public init(isPresented: Binding) { self._isPresented = isPresented print(DEBUG: JobCreationView ini
1
0
124
Apr ’25
SwiftData Lightweight Migraton failed with VersionedSchema
Setup I am running a versionedSchema for my SwiftData model and attempting a migration. The new version contains a new attribute, with a type of a new custom enum defined in the @Model class, a default value, and a private(set). Migration was completed with a migrationPlan with nil values for willMigrate and didMigrate. Example - Previous Version @Model class MyNumber { var num: Int init() { // Init Code } } Example - Newest Version @Model class MyNumber { var num: Int private(set) var rounding: RoundAmount = MyNumber.RoundAmount.thirtyMinute init() { // Init Code } enum RoundAmount { case fiveMinute, tenMinute, thirtyMinute } } Issue Running this code, I get a swiftData error for “SwiftData/ModelCoders.swift:1585: nil value passed for a non-optional keyPath, /MyNumber.rounding” I assume this means a failure of the swiftData lightweight migration? I have reverted the version, removed private(set) and re-tried the migration with no success. Using the versionedSchema with mig
1
0
130
Apr ’25
Reply to Xcode 16.3 / macOS 15.4: SwiftData ModelContainer 在关联 iCloud Container 后初始化时崩溃
When you create a ModelConfiguration, the default value of the cloudKitDatabase attribute .automatic, which tells SwiftData to enable CloudKit synchronization using the primary CloudKit container from the app’s entitlements. That is why you see that SwiftData automatically picks up the CloudKit container, if you configure one in your project, and enables CloudKit integration. If you don't like the default behavior, pass .none when you create the model configuration. Assuming that you use the Xcode template code to trigger the crash, most likely, you will see the following message in your Xcode console: Unresolved error loading container Error Domain=NSCocoaErrorDomain Code=134060 A Core Data error occurred. UserInfo={NSLocalizedFailureReason=CloudKit integration requires that all attributes be optional, or have a default value set. The following attributes are marked non-optional but do not have a default value: Item: timestamp} The log makes clear that the failure is triggered because Item:
Apr ’25
Xcode 16.3 / macOS 15.4: SwiftData ModelContainer 在关联 iCloud Container 后初始化时崩溃
问题描述: 环境: Xcode 版本: 16.3 *macOS 版本: 15.4 项目类型: SwiftUI App with SwiftData 问题摘要: 当在 Xcode 项目的 Signing & Capabilities 中为启用了 iCloud 能力的应用关联一个具体的 iCloud Container 时,即使代码中并未显式启用 CloudKit 同步(例如,未在 ModelConfiguration 中设置 cloudKitDatabase),SwiftData 的 ModelContainer 在应用启动初始化时也会立即失败并导致崩溃。如果仅启用 iCloud 能力但不选择任何 Container,应用可以正常启动。此问题在使用空的 Schema([]) 进行测试时依然稳定复现。 复现步骤 (使用最小复现项目 - MRE): 使用 Xcode 16.3 创建一个新的 SwiftUI App 项目 (例如,命名为 CloudKitCrashTest)。 在创建时不要勾选 Host in CloudKit,或者,如果勾选了,先确保后续步骤覆盖相关设置。Storage 选择 None 或 SwiftData 均可复现。 修改 CloudKitCrashTestApp.swift 文件,添加 SwiftData 导入和基本的 ModelContainer 初始化逻辑。关键代码如下: import SwiftUI import SwiftData @main struct CloudKitCrashTestApp: App { let sharedModelContainer: ModelContainer init() { // 使用空 Schema 进行诊断 let schema = Schema([]) // *不* 指定 cloudKitDatabase let modelConfiguration = ModelConfiguration(schema: schema, isStoredInMemoryOnly: false) do { sharedModelContainer = try ModelContainer(for: schema, configurations: [modelConfi
2
0
464
Apr ’25
SwiftData data crashes with @Relationship
I've noticed that SwiftData's @Relationship seems to potentially cause application crashes. The crash error is shown in the image. Since this crash appears to be random and I cannot reproduce it under specific circumstances, I can only temporarily highlight that this issue seems to exist. @Model final class TrainInfo { @Relationship(deleteRule: .cascade, inverse: StopStation.trainInfo) var stations: [StopStation]? } @Model final class StopStation { @Relationship var trainInfo: TrainInfo? } /// some View var origin: StopStationDisplayable? { if let train = train as? TrainInfo { return train.stations?.first(where: { $0.isOrigin }) ?? train.stations?.first(where: { $0.isStarting }) } return nil } // Some other function or property func someFunction() { if let origin, let destination { // Function implementation } }
1
0
154
Apr ’25
Reply to SwiftData data crashes with @Relationship
The stack trace seems to indicate that your code was trying to retrieve the value of an attribute, but the attribute didn't exist in the SwiftData model. The code snippet shows that TrainInfo and StopStation is a to-many relationship, which has nothing wrong. isOrigin and isStarting seem to be an attribute of StopStation. They are not included in your code snippet, and so I can't comment. Overall, the information you provided doesn't seem to be enough to diagnose the issue... Best, —— Ziqiao Chen  Worldwide Developer Relations.
Apr ’25
SwiftData migration crashes when working with relationships
The following complex migration consistently crashes the app with the following error: SwiftData/PersistentModel.swift:726: Fatal error: What kind of backing data is this? SwiftData._KKMDBackingData My app relies on a complex migration that involves these optional 1 to n relationships. Theoretically I could not assign the relationships in the willMigrate block but afterwards I am not able to tell which list and items belonged together. Steps to reproduce: Run project Change typealias CurrentSchema to ItemSchemaV2 instead of ItemSchemaV1. Run project again -> App crashes My setup: Xcode Version 16.2 (16C5032a) MacOS Sequoia 15.4 iPhone 12 with 18.3.2 (22D82) Am I doing something wrong or did I stumble upon a bug? I have a demo Xcode project ready but I could not upload it here so I put the code below. Thanks for your help typealias CurrentSchema = ItemSchemaV1 typealias ItemList = CurrentSchema.ItemList typealias Item = CurrentSchema.Item @main struct SwiftDataMigrationAp
1
0
185
Apr ’25
Reply to SwiftData migration crashes when working with relationships
Theoretically I could not assign the relationships in the willMigrate block Yeah, the context passed to willMigrate is tied to the existing store, which doesn't have the knowledge of your new schema, and so trying to persisting an ItemSchemaV2 object, which I believe is a part of the new schema, will fail. You can consider do the data transformation in didMigrate, where the context is tied to the migrated store, which allows you to access the new schema. but afterwards I am not able to tell which list and items belonged together. Would you mind to share why? When didMigrate is called, ItemSchemaV1.Item and ItemSchemaV1.ItemList have been migrated to ItemSchemaV2.Item and ItemSchemaV2.ItemList, and so you can still fetch the item list from ItemSchemaV2.ItemList, update ItemSchemaV2.ItemList.note, and save the change, can't you? Best, —— Ziqiao Chen  Worldwide Developer Relations.
Apr ’25
Reply to SwiftUI & SwiftData: Fatal Error "Duplicate keys of type" Occurs on First Launch
Was just dealing with the same thing, and removing the id: .self from a ForEach I just added seems to have solved it - thanks! As to the reason, my guess is that SwiftUI is holding a Dictionary of every object, using the id: value as the key - SwiftData is likely mutating these objects behind the scenes, to reload data, fault data, etc. That would cause this error to happen. Omitting the id: parameter in the ForEach, or using id: .id would use the stable identifier as the key of the 'hidden' Dictionary, therefore eliminating the issue. All of that makes sense to me, at least - unfortunately, we use id: .self so frequently, that I can almost guarantee that I'll make this mistake again in the future. Would be nice if making this error were impossible, or if Xcode had a way to warn us about it.
Apr ’25
SwiftUI & SwiftData: Fatal Error "Duplicate keys of type" Occurs on First Launch
I'm developing a SwiftUI app using SwiftData and encountering a persistent issue: Error Message: Thread 1: Fatal error: Duplicate keys of type 'Bland' were found in a Dictionary. This usually means either that the type violates Hashable's requirements, or that members of such a dictionary were mutated after insertion. Details: Occurrence: The error always occurs on the first launch of the app after installation. Specifically, it happens approximately 1 minute after the app starts. Inconsistent Behavior: Despite no changes to the code or server data, the error occurs inconsistently. Data Fetching Process: I fetch data for entities (Bland, CrossZansu, and Trade) from the server using the following process: Fetch Bland and CrossZansu entities via URLSession. Insert or update these entities into the SwiftData context. The fetched data is managed as follows: func refleshBlandsData() async throws { if let blandsOnServer = try await DataModel.shared.getBlands() { await MainActor.run { blandsOnServe
3
0
642
Apr ’25
How to diagnose spurious SwiftDataMacros error
I have a Package.swift file that builds and runs from Xcode 15.2 without issue but fails to compile when built from the command line (swift build). The swift version is 6.0.3. I'm at wits end trying to diagnose this and would welcome any thoughts. The error in question is error: external macro implementation type 'SwiftDataMacros.PersistentModelMacro' could not be found for macro 'Model()'; plugin for module 'SwiftDataMacros' not found The code associated with the module is very vanilla. import Foundation import SwiftData @Model public final class MyObject { @Attribute(.unique) public var id:Int64 public var vertexID:Int64 public var updatedAt:Date public var codeUSRA:Int32 init(id:Int64, vertexID:Int64, updatedAt:Date, codeUSRA:Int32) { self.id = id self.vertexID = vertexID self.updatedAt = updatedAt self.codeUSRA = codeUSRA } public static func create(id:Int64, vertexID:Int64, updatedAt:Date, codeUSRA:Int32) -> MyObject { MyObject(id: id, vertexID: vertexID, updatedAt: updatedAt, codeUSRA: codeU
1
0
350
Apr ’25
HealthKit SwiftData sync
Hello, I want to build an app that will allow the user to entry some health related records and be synced with the HealthKit. Any record that is in the HealthKit is stored locally on the device. I find it conceptually unsure if I should be storing the HealthKit records in the SwiftData to make the user records available across the iCloud synced devices. Should I read the HealthKit record, make a copy of it (including it's ID) on my app's data in SwiftData? How the syncing should be done the right way? thanks.
2
0
1.1k
May ’24
Reply to HealthKit SwiftData sync
I’m also building a health app. How do I handle a situation where the user doesn’t want to grant Health access, but I want my app to be able to still function using local data via SwiftData? How would these two data stores coexist if the user later grants health access?
Apr ’25
Reply to Xcode? Hacking? Iphone11
hello, first my disclaimer...I am very new to Apple products and my knowledge base is minimal. That said, I have immersed myself in an effort to learn all I possibly can about all topics related to being hacked, because I have also been invaded. i will summarize my experiences and offer a nugget or two of gathered wisdom. i believe the invasion (access to my device) was not physical, and i think it began through using information held only by my provider. **Incidentally, in a separate though related research project, and with info gathered specific to corporate ownership, parent-child relationships, patterns found in company formation/agent for process data/physical addresses offered publicly through registration documentation, and probably more that I do not recall right now...I think I know the person who owns, or has financial control of, my cellular carrier. I will add that this person owns and controls many nationally known companies but disconnects himself by using proxy synthetic identities to
Apr ’25
error: the replacement path doesn't exist <- how bad is this error, should i care - is it important?
I get this error, i have my own DIKit, and i want to use swiftdata for showing info from persisten model. It works all over the app, but i get this error with my .sheet. // JobCreationView.swift // Features // // Created by Jens Vik on 26/03/2025. // import SwiftUI import DesignKit import DIKit import PresentationKit import CoreKit import DomainKit import SwiftData public struct JobCreationView: View { @Binding var isPresented: Bool // Inject view model using DIKit's property wrapper @Injected((any JobCreationViewModelProtocol).self) private var viewModel // Form state @Injected(ModelContext.self) private var modelContext @State private var date = Date() @State private var isASAP = false @State private var price = @State private var jobType = Fiks @State private var description = // Available job types private let jobTypes = [Fiks, Fiksit] @Query private var userContexts: [UserContextModel] public init(isPresented: Binding) { self._isPresented = isPresented print(DEBUG: JobCreationView ini
Replies
1
Boosts
0
Views
124
Activity
Apr ’25
SwiftData Lightweight Migraton failed with VersionedSchema
Setup I am running a versionedSchema for my SwiftData model and attempting a migration. The new version contains a new attribute, with a type of a new custom enum defined in the @Model class, a default value, and a private(set). Migration was completed with a migrationPlan with nil values for willMigrate and didMigrate. Example - Previous Version @Model class MyNumber { var num: Int init() { // Init Code } } Example - Newest Version @Model class MyNumber { var num: Int private(set) var rounding: RoundAmount = MyNumber.RoundAmount.thirtyMinute init() { // Init Code } enum RoundAmount { case fiveMinute, tenMinute, thirtyMinute } } Issue Running this code, I get a swiftData error for “SwiftData/ModelCoders.swift:1585: nil value passed for a non-optional keyPath, /MyNumber.rounding” I assume this means a failure of the swiftData lightweight migration? I have reverted the version, removed private(set) and re-tried the migration with no success. Using the versionedSchema with mig
Replies
1
Boosts
0
Views
130
Activity
Apr ’25
Reply to SwiftData Lightweight Migraton failed with VersionedSchema
Yeah, enum RoundAmount is not Codable and so SwiftData doesn't know how to encode / decode MyNumber.rounding. You can fix the issue by making your enum Codable, like below: enum RoundAmount: Int, Codable { case fiveMinute = 5, tenMinute = 10, thirtyMinute = 30 } Best, —— Ziqiao Chen  Worldwide Developer Relations.
Replies
Boosts
Views
Activity
Apr ’25
Reply to Xcode 16.3 / macOS 15.4: SwiftData ModelContainer 在关联 iCloud Container 后初始化时崩溃
When you create a ModelConfiguration, the default value of the cloudKitDatabase attribute .automatic, which tells SwiftData to enable CloudKit synchronization using the primary CloudKit container from the app’s entitlements. That is why you see that SwiftData automatically picks up the CloudKit container, if you configure one in your project, and enables CloudKit integration. If you don't like the default behavior, pass .none when you create the model configuration. Assuming that you use the Xcode template code to trigger the crash, most likely, you will see the following message in your Xcode console: Unresolved error loading container Error Domain=NSCocoaErrorDomain Code=134060 A Core Data error occurred. UserInfo={NSLocalizedFailureReason=CloudKit integration requires that all attributes be optional, or have a default value set. The following attributes are marked non-optional but do not have a default value: Item: timestamp} The log makes clear that the failure is triggered because Item:
Replies
Boosts
Views
Activity
Apr ’25
Xcode 16.3 / macOS 15.4: SwiftData ModelContainer 在关联 iCloud Container 后初始化时崩溃
问题描述: 环境: Xcode 版本: 16.3 *macOS 版本: 15.4 项目类型: SwiftUI App with SwiftData 问题摘要: 当在 Xcode 项目的 Signing & Capabilities 中为启用了 iCloud 能力的应用关联一个具体的 iCloud Container 时,即使代码中并未显式启用 CloudKit 同步(例如,未在 ModelConfiguration 中设置 cloudKitDatabase),SwiftData 的 ModelContainer 在应用启动初始化时也会立即失败并导致崩溃。如果仅启用 iCloud 能力但不选择任何 Container,应用可以正常启动。此问题在使用空的 Schema([]) 进行测试时依然稳定复现。 复现步骤 (使用最小复现项目 - MRE): 使用 Xcode 16.3 创建一个新的 SwiftUI App 项目 (例如,命名为 CloudKitCrashTest)。 在创建时不要勾选 Host in CloudKit,或者,如果勾选了,先确保后续步骤覆盖相关设置。Storage 选择 None 或 SwiftData 均可复现。 修改 CloudKitCrashTestApp.swift 文件,添加 SwiftData 导入和基本的 ModelContainer 初始化逻辑。关键代码如下: import SwiftUI import SwiftData @main struct CloudKitCrashTestApp: App { let sharedModelContainer: ModelContainer init() { // 使用空 Schema 进行诊断 let schema = Schema([]) // *不* 指定 cloudKitDatabase let modelConfiguration = ModelConfiguration(schema: schema, isStoredInMemoryOnly: false) do { sharedModelContainer = try ModelContainer(for: schema, configurations: [modelConfi
Replies
2
Boosts
0
Views
464
Activity
Apr ’25
SwiftData data crashes with @Relationship
I've noticed that SwiftData's @Relationship seems to potentially cause application crashes. The crash error is shown in the image. Since this crash appears to be random and I cannot reproduce it under specific circumstances, I can only temporarily highlight that this issue seems to exist. @Model final class TrainInfo { @Relationship(deleteRule: .cascade, inverse: StopStation.trainInfo) var stations: [StopStation]? } @Model final class StopStation { @Relationship var trainInfo: TrainInfo? } /// some View var origin: StopStationDisplayable? { if let train = train as? TrainInfo { return train.stations?.first(where: { $0.isOrigin }) ?? train.stations?.first(where: { $0.isStarting }) } return nil } // Some other function or property func someFunction() { if let origin, let destination { // Function implementation } }
Replies
1
Boosts
0
Views
154
Activity
Apr ’25
Reply to SwiftData data crashes with @Relationship
The stack trace seems to indicate that your code was trying to retrieve the value of an attribute, but the attribute didn't exist in the SwiftData model. The code snippet shows that TrainInfo and StopStation is a to-many relationship, which has nothing wrong. isOrigin and isStarting seem to be an attribute of StopStation. They are not included in your code snippet, and so I can't comment. Overall, the information you provided doesn't seem to be enough to diagnose the issue... Best, —— Ziqiao Chen  Worldwide Developer Relations.
Replies
Boosts
Views
Activity
Apr ’25
SwiftData migration crashes when working with relationships
The following complex migration consistently crashes the app with the following error: SwiftData/PersistentModel.swift:726: Fatal error: What kind of backing data is this? SwiftData._KKMDBackingData My app relies on a complex migration that involves these optional 1 to n relationships. Theoretically I could not assign the relationships in the willMigrate block but afterwards I am not able to tell which list and items belonged together. Steps to reproduce: Run project Change typealias CurrentSchema to ItemSchemaV2 instead of ItemSchemaV1. Run project again -> App crashes My setup: Xcode Version 16.2 (16C5032a) MacOS Sequoia 15.4 iPhone 12 with 18.3.2 (22D82) Am I doing something wrong or did I stumble upon a bug? I have a demo Xcode project ready but I could not upload it here so I put the code below. Thanks for your help typealias CurrentSchema = ItemSchemaV1 typealias ItemList = CurrentSchema.ItemList typealias Item = CurrentSchema.Item @main struct SwiftDataMigrationAp
Replies
1
Boosts
0
Views
185
Activity
Apr ’25
Reply to SwiftData migration crashes when working with relationships
Theoretically I could not assign the relationships in the willMigrate block Yeah, the context passed to willMigrate is tied to the existing store, which doesn't have the knowledge of your new schema, and so trying to persisting an ItemSchemaV2 object, which I believe is a part of the new schema, will fail. You can consider do the data transformation in didMigrate, where the context is tied to the migrated store, which allows you to access the new schema. but afterwards I am not able to tell which list and items belonged together. Would you mind to share why? When didMigrate is called, ItemSchemaV1.Item and ItemSchemaV1.ItemList have been migrated to ItemSchemaV2.Item and ItemSchemaV2.ItemList, and so you can still fetch the item list from ItemSchemaV2.ItemList, update ItemSchemaV2.ItemList.note, and save the change, can't you? Best, —— Ziqiao Chen  Worldwide Developer Relations.
Replies
Boosts
Views
Activity
Apr ’25
Reply to SwiftUI & SwiftData: Fatal Error "Duplicate keys of type" Occurs on First Launch
Was just dealing with the same thing, and removing the id: .self from a ForEach I just added seems to have solved it - thanks! As to the reason, my guess is that SwiftUI is holding a Dictionary of every object, using the id: value as the key - SwiftData is likely mutating these objects behind the scenes, to reload data, fault data, etc. That would cause this error to happen. Omitting the id: parameter in the ForEach, or using id: .id would use the stable identifier as the key of the 'hidden' Dictionary, therefore eliminating the issue. All of that makes sense to me, at least - unfortunately, we use id: .self so frequently, that I can almost guarantee that I'll make this mistake again in the future. Would be nice if making this error were impossible, or if Xcode had a way to warn us about it.
Replies
Boosts
Views
Activity
Apr ’25
SwiftUI & SwiftData: Fatal Error "Duplicate keys of type" Occurs on First Launch
I'm developing a SwiftUI app using SwiftData and encountering a persistent issue: Error Message: Thread 1: Fatal error: Duplicate keys of type 'Bland' were found in a Dictionary. This usually means either that the type violates Hashable's requirements, or that members of such a dictionary were mutated after insertion. Details: Occurrence: The error always occurs on the first launch of the app after installation. Specifically, it happens approximately 1 minute after the app starts. Inconsistent Behavior: Despite no changes to the code or server data, the error occurs inconsistently. Data Fetching Process: I fetch data for entities (Bland, CrossZansu, and Trade) from the server using the following process: Fetch Bland and CrossZansu entities via URLSession. Insert or update these entities into the SwiftData context. The fetched data is managed as follows: func refleshBlandsData() async throws { if let blandsOnServer = try await DataModel.shared.getBlands() { await MainActor.run { blandsOnServe
Replies
3
Boosts
0
Views
642
Activity
Apr ’25
How to diagnose spurious SwiftDataMacros error
I have a Package.swift file that builds and runs from Xcode 15.2 without issue but fails to compile when built from the command line (swift build). The swift version is 6.0.3. I'm at wits end trying to diagnose this and would welcome any thoughts. The error in question is error: external macro implementation type 'SwiftDataMacros.PersistentModelMacro' could not be found for macro 'Model()'; plugin for module 'SwiftDataMacros' not found The code associated with the module is very vanilla. import Foundation import SwiftData @Model public final class MyObject { @Attribute(.unique) public var id:Int64 public var vertexID:Int64 public var updatedAt:Date public var codeUSRA:Int32 init(id:Int64, vertexID:Int64, updatedAt:Date, codeUSRA:Int32) { self.id = id self.vertexID = vertexID self.updatedAt = updatedAt self.codeUSRA = codeUSRA } public static func create(id:Int64, vertexID:Int64, updatedAt:Date, codeUSRA:Int32) -> MyObject { MyObject(id: id, vertexID: vertexID, updatedAt: updatedAt, codeUSRA: codeU
Replies
1
Boosts
0
Views
350
Activity
Apr ’25
HealthKit SwiftData sync
Hello, I want to build an app that will allow the user to entry some health related records and be synced with the HealthKit. Any record that is in the HealthKit is stored locally on the device. I find it conceptually unsure if I should be storing the HealthKit records in the SwiftData to make the user records available across the iCloud synced devices. Should I read the HealthKit record, make a copy of it (including it's ID) on my app's data in SwiftData? How the syncing should be done the right way? thanks.
Replies
2
Boosts
0
Views
1.1k
Activity
May ’24
Reply to HealthKit SwiftData sync
I’m also building a health app. How do I handle a situation where the user doesn’t want to grant Health access, but I want my app to be able to still function using local data via SwiftData? How would these two data stores coexist if the user later grants health access?
Replies
Boosts
Views
Activity
Apr ’25
Reply to Xcode? Hacking? Iphone11
hello, first my disclaimer...I am very new to Apple products and my knowledge base is minimal. That said, I have immersed myself in an effort to learn all I possibly can about all topics related to being hacked, because I have also been invaded. i will summarize my experiences and offer a nugget or two of gathered wisdom. i believe the invasion (access to my device) was not physical, and i think it began through using information held only by my provider. **Incidentally, in a separate though related research project, and with info gathered specific to corporate ownership, parent-child relationships, patterns found in company formation/agent for process data/physical addresses offered publicly through registration documentation, and probably more that I do not recall right now...I think I know the person who owns, or has financial control of, my cellular carrier. I will add that this person owns and controls many nationally known companies but disconnects himself by using proxy synthetic identities to
Replies
Boosts
Views
Activity
Apr ’25