Search results for

“LLDB crash”

30,542 results found

Post

Replies

Boosts

Views

Activity

SwiftData: This model instance was invalidated because its backing data could no longer be found the store
Hello 👋, I encounter the This model instance was invalidated because its backing data could no longer be found the store crash with SwiftData. Which from what I understood means I try to access a model after it has been removed from the store (makes sense). I made a quick sample to reproduce/better understand because there some case(s) I can't figure it out. Let's take a concrete example, we have Home model and a Home can have many Room(s). // Sample code @MainActor let foo = Foo() // A single reference let database = Database(modelContainer: sharedModelContainer) // A single reference @MainActor class Foo { // Properties to explicilty keep reference of model(s) for the purpose of the POC var _homes = [Home]() var _rooms = [Room]() func fetch() async { let homes = await database.fetch().map { sharedModelContainer.mainContext.model(for: $0) as! Home } print(ObjectIdentifier(homes[0]), homes[0].rooms?.map(.id)) // This will crash here or not. } // Same version of a delete function with subtle
2
0
274
Nov ’25
Reply to Persistent font registration crashes when fonts are delivered via Apple-Hosted Background Assets
[quote='867195022, Sandya, /thread/808036?answerId=867195022#867195022, /profile/Sandya'] This does prevent the crash. [/quote] Cool. [quote='867195022, Sandya, /thread/808036?answerId=867195022#867195022, /profile/Sandya'] the fonts still do not install system-wide [/quote] Bummer. [quote='867195022, Sandya, /thread/808036?answerId=867195022#867195022, /profile/Sandya'] Is .persistent font registration intended to work with fonts delivered through Apple-Hosted Background Assets? [/quote] I don’t know, but I’m not sure that matters. You want this to work, and that’s a pretty reasonable request. So either this as a bug or an enhancement request, and the path forward is the same in both cases: File a report in Feedback Assistant. However, looking at FB21109320 it seems like we’ve decided to use it to drive that investigation, rather than use it to track the CT annotation issue. So I don’t think there’s anything else for you to do here, other than to keep on eye on FB21109320 in Feedback Assistant. Shar
Nov ’25
Reply to How to close / cancel a NetworkConnection
There’s no explicit cancel method in the new API. Rather, our expectation is that you’d use structure concurrency, meaning that: All the use of a given connection would be within one scope. When you exit that scope, that drops the last reference to the connection. Which then cancels it. There’s a similar setup for listeners and browser, except those enforce the rules by means of their run(…) methods. [quote='808198021, captadoh, /thread/808198, /profile/captadoh'] my app crashes when I go to toggle of all the networking stuff. [/quote] Can you share an example crash report? See Posting a Crash Report for advice on how to do that. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Nov ’25
How to close / cancel a NetworkConnection
Hello, I have an app that was using the iOS 18 Network Framework APIs. It used Peer to Peer, QUIC and Bonjour. It was all working as expected. I wanted to upgrade to the new iOS 26 Network Framework APIs (NetworkBrowser, NetworkListener, NetworkConnection...). I have things working (multiple devices can discover each other, connection to each other and send messages to each other) but my app crashes when I go to toggle of all the networking stuff. In the iOS 18 Network Framework API NWConnection had a .cancel() function I could use to tell the other side the connection was done. I dont see a cancel function for NetworkConnection. My question is - how do I properly close down a NetworkConnection and also properly tell the other side the connection is done.
2
0
205
Nov ’25
Sign in with Apple error reported by App Review, but impossible to reproduce (iPadOS 26.1)
Hi everyone, I’m currently facing a blocking issue during App Review, and I’d really appreciate some help from anyone who has experienced something similar. My app was rejected under Guideline 2.1 – App Completeness with the following message: “An error message appeared after trying to Sign in with Apple. Device: iPad Air (5th generation), iPadOS 26.1.” The problem is: I cannot reproduce this bug at all, even when testing under the same conditions. ✔ What I tested: Physical iPad Air M2 on iPadOS 26.1 Physical iPhone devices iOS/iPadOS simulators (latest Xcode) TestFlight build (clean install) Debug build installed via Xcode (device connected) In every case, Sign in with Apple works correctly: Authentication sheet displays properly Callback returns the credential User is created/logged in without error No crash, no rejected promise, no empty credential ✔ Environment Using ASAuthorizationAppleIDProvider + ASAuthorizationController Default Apple Sign In button No custom nonce/redirect modifications No b
1
0
186
Nov ’25
LLVM Linker Crash on ARM64 with bfloat16 Symbols (Xcode 17.0.0)
LLVM Linker Crash on ARM64 with bfloat16 Symbols (Xcode 17.0.0) We're encountering a critical linker crash in Xcode 17.0.0 (clang-1700.4.4.1) on macOS 15.1.0 (Darwin 25.1.0) with Apple Silicon M3 Max when linking a pybind11 C++ extension against the MLX framework (v0.30.1). The linker consistently crashes with LLVM ERROR: No way to correctly truncate anything but float to bfloat during the linking phase, even though our code uses only integer types (int64, uint32) for BPE tokenization and never directly references bfloat16 types. Error Details: [100%] Linking CXX shared module _metal_trainer.cpython-312-darwin.so LLVM ERROR: No way to correctly truncate anything but float to bfloat clang++: error: unable to execute command: Abort trap: 6 clang++: error: linker command failed due to signal (use -v to see invocation) Reproduction: Install MLX framework: pip install mlx (any version with bfloat16 support) Create a minimal pybind11 extension that links against MLX: Compiler: AppleClang
1
0
211
Nov ’25
Reply to DEXT (IOUserSCSIParallelInterfaceController): Direct I/O Succeeds, but Buffered I/O Fails with Data Corruption on Large File Copies
Hi Kevin, Regarding your previous analysis of the KEXT configuration, specifically where you pointed out the IOMaximumByteCount is actually 0x80000 (512KB) in this post. We observed the runtime logs of the legacy KEXT, and the results align perfectly with your observation. Even when copying a 2GB file, the KEXT actually splits the request into 512KB (0x80000) chunks per transfer. [ProcessParallelTask] [KEXT_CHECK] WRITE (0x2a) | T:0 L:0 | Size: 524288 bytes (512 KB) This confirms that our current 1MB limit in the DEXT actually exceeds the behavior of the legacy driver. Since the current setting has passed all data integrity verifications, we consider the transfer size issue resolved and will not pursue larger transfer sizes at this stage. As per your recommendation, we are currently implementing the UserProcessBundledParallelTasks architecture to strictly follow DriverKit best practices and optimize performance (it is currently causing the DEXT to crash, so we are in the middle of debugging it). Than
Topic: App & System Services SubTopic: Drivers Tags:
Nov ’25
crash while exectuing __llvm_profile_write_file() in Xcode26.0
I am developing an iOS in-app SDK for collecting code coverage data. The SDK writes coverage data to a specified file by calling __llvm_profile_set_filename and __llvm_profile_write_file. This implementation worked correctly until I switched to Xcode 26.0 to build my project. Now, when __llvm_profile_write_file() is executed, it crashes with the following error stack. Can anyone provide any assistance? Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Subtype: KERN_INVALID_ADDRESS at 0x0000000000000001 Exception Codes: 0x0000000000000001, 0x0000000000000001 Termination Reason: Namespace SIGNAL, Code 11, Segmentation fault: 11 Terminating Process: exc handler [454] Thread 96 name: Dispatch queue: com.test-coverage.processing Thread 96: Crashed: 0 Demo 0x122602ea8 initializeValueProfRuntimeRecord (in Demo) (InstrProfilingValue.c:351) 1 Demo 0x00000001226064c0 writeOneValueProfData (in Demo) (InstrProfilingWriter.c:153) 2 Demo 0x0000000122606308 writeValueProfData (in Demo) (InstrProfilingWrit
0
0
262
Nov ’25
DeclaredAgeRange framework new cases and properties cause runtime crash with missing symbol
I'm making a wrapper library to abstract away some of the 'missing platform support' of DeclaredAgeRange until hopefully it expands to additional platforms. When I'm trying to fully enumerate all of the cases of AgeRangeDeclaration, which they all state available starting 26.0 (mysteriously added in Xcode 26.2 beta), the app crashes due to a missing symbol at launch time. This happens both for Xcode 26.1, 26.2 beta 2, and matching Xcode Cloud builds. So I've isolated it beyond doesn't work on my machine. I just made a handful of crashes and attached a sysdiagnose to a fresh feedback. FB21121092 - DeclaredAgeRange: Eligibility property and new declaration cases unavailable on iOS 26.1 device contradicting documentation - causes runtime symbol not found crash If anyone is curious what these crashes look like I've attached the DiagnosticPayload.jsonRepresentation() generated from one of my favorite frameworks, MetricKit. Very clearly articulated in the diagnostic metadata you
5
0
1k
Nov ’25
Reply to Lock Contention in APFS/Kernel?
So I guess I'm wondering: is it... fine to now use fdatasync on APFS? Because if it is now fine (as per sqlite's understanding via the Hacker News comment...), then I think there's a bunch of software might be relying on outdated documentation/advice, since: So, the first thing to understand is that what led to F_FULLFSYNC wasn't really the kernel itself's handling of data. The basic issue was that the kernel itself would send the data all the way to disk... and which point the drive itself would stick the data in a write cache and leave it there for an indeterminate but long time. Even worse: Some of these drives were intentionally ignoring the existing commands (and more performant) that were supposed to flush the specific data. These issue were widespread enough across product and vendors that blaming hardware wasn't really feasible. The only solution we found viable was what F_FULLFSYNC does, which is to flush the data and the force the drive to commit the data. I'll also note that issue above was never s
Topic: App & System Services SubTopic: Core OS Tags:
Nov ’25
Reply to Age Range API - Sandbox Testing Available
Using Xcode 26.2, targeting an iPhone 17 Pro running 26.1, Xcode crashes saying the symbol isn't available. The isEligibleForAgeFeatures property is actually available in iOS 26.2 beta or later. The documentation showing it as iOS 26 is a bug. Thank you for filing your Feedback report. Upgrade your device to iOS 26.2 beta to test it.
Topic: App & System Services SubTopic: General Tags:
Nov ’25
Reply to Persistent font registration crashes when fonts are delivered via Apple-Hosted Background Assets
Hi Quinn, Thank you for the detailed analysis — especially the breakdown of the crashing thread and explanation about the Swift concurrency actor expectation. That was extremely helpful. I tested your suggestion: CTFontManagerRegisterFontURLs(cfArray, scope, true) { @Sendable _, _ in true } Result This does prevent the crash. The system “Install Fonts” sheet appears, and tapping Install no longer triggers a trap. Remaining Issue Although the crash is fixed, the fonts still do not install system-wide when using the .persistent scope with fonts delivered via Apple-Hosted Background Assets. After tapping Install, nothing appears under: Settings → General → Fonts → My Fonts So the concurrency crash is resolved, but the underlying issue remains: .process registration works .persistent registration does not install fonts No errors are returned by CTFontManagerRegisterFontURLs Next Steps As you suggested, I am happy to have FB21109320 repurposed to track the missing concurrency an
Nov ’25
Reply to SwiftData not loading under iOS 26.1
Hello again, So, they are two issues. The crash and the iCloud sync dealing with this new @Attribute trasformables that Apple change for us and thus, provoking this mess. In all honestly, Apple is the one that should be making the Tweaks, not us. In-memory models should respect the existing data store of our Apps since they are already being used by thousands of users in realtime. Someone above probably doesn't want to deal with the iOS26.2 publishing date (it's in the final stages) and that is the wrong decision. Why do we have to clean the mess when Apple made our code incompatible? 😒. Makes no sense. ** ** Are you aware how many weeks of work it will take for us to refactor all of our Apps using this confusing tweak with decodables? Sorry but your solution is not acceptable.
Nov ’25
SwiftData: This model instance was invalidated because its backing data could no longer be found the store
Hello 👋, I encounter the This model instance was invalidated because its backing data could no longer be found the store crash with SwiftData. Which from what I understood means I try to access a model after it has been removed from the store (makes sense). I made a quick sample to reproduce/better understand because there some case(s) I can't figure it out. Let's take a concrete example, we have Home model and a Home can have many Room(s). // Sample code @MainActor let foo = Foo() // A single reference let database = Database(modelContainer: sharedModelContainer) // A single reference @MainActor class Foo { // Properties to explicilty keep reference of model(s) for the purpose of the POC var _homes = [Home]() var _rooms = [Room]() func fetch() async { let homes = await database.fetch().map { sharedModelContainer.mainContext.model(for: $0) as! Home } print(ObjectIdentifier(homes[0]), homes[0].rooms?.map(.id)) // This will crash here or not. } // Same version of a delete function with subtle
Replies
2
Boosts
0
Views
274
Activity
Nov ’25
Reply to Persistent font registration crashes when fonts are delivered via Apple-Hosted Background Assets
[quote='867195022, Sandya, /thread/808036?answerId=867195022#867195022, /profile/Sandya'] This does prevent the crash. [/quote] Cool. [quote='867195022, Sandya, /thread/808036?answerId=867195022#867195022, /profile/Sandya'] the fonts still do not install system-wide [/quote] Bummer. [quote='867195022, Sandya, /thread/808036?answerId=867195022#867195022, /profile/Sandya'] Is .persistent font registration intended to work with fonts delivered through Apple-Hosted Background Assets? [/quote] I don’t know, but I’m not sure that matters. You want this to work, and that’s a pretty reasonable request. So either this as a bug or an enhancement request, and the path forward is the same in both cases: File a report in Feedback Assistant. However, looking at FB21109320 it seems like we’ve decided to use it to drive that investigation, rather than use it to track the CT annotation issue. So I don’t think there’s anything else for you to do here, other than to keep on eye on FB21109320 in Feedback Assistant. Shar
Replies
Boosts
Views
Activity
Nov ’25
Reply to How to close / cancel a NetworkConnection
There’s no explicit cancel method in the new API. Rather, our expectation is that you’d use structure concurrency, meaning that: All the use of a given connection would be within one scope. When you exit that scope, that drops the last reference to the connection. Which then cancels it. There’s a similar setup for listeners and browser, except those enforce the rules by means of their run(…) methods. [quote='808198021, captadoh, /thread/808198, /profile/captadoh'] my app crashes when I go to toggle of all the networking stuff. [/quote] Can you share an example crash report? See Posting a Crash Report for advice on how to do that. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Replies
Boosts
Views
Activity
Nov ’25
Reply to Xcode 26.1 is crashing when I try to import the .icon from Icon Composer
The crash logs are the following: Triggered by Thread: 0, Dispatch Queue: com.apple.main-thread Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: Namespace SIGNAL, Code 6, Abort trap: 6 Terminating Process: Xcode [75596]
Replies
Boosts
Views
Activity
Nov ’25
Xcode 26.1 is crashing when I try to import the .icon from Icon Composer
I've made my updated icon and I try to import it to Xcode but it keeps crashing even if I clean the project/delete derived data or try to add through the Naivgation Controls. I've tried with the Xcode 26.2 beta too but it has the same issue.
Replies
1
Boosts
0
Views
99
Activity
Nov ’25
How to close / cancel a NetworkConnection
Hello, I have an app that was using the iOS 18 Network Framework APIs. It used Peer to Peer, QUIC and Bonjour. It was all working as expected. I wanted to upgrade to the new iOS 26 Network Framework APIs (NetworkBrowser, NetworkListener, NetworkConnection...). I have things working (multiple devices can discover each other, connection to each other and send messages to each other) but my app crashes when I go to toggle of all the networking stuff. In the iOS 18 Network Framework API NWConnection had a .cancel() function I could use to tell the other side the connection was done. I dont see a cancel function for NetworkConnection. My question is - how do I properly close down a NetworkConnection and also properly tell the other side the connection is done.
Replies
2
Boosts
0
Views
205
Activity
Nov ’25
Sign in with Apple error reported by App Review, but impossible to reproduce (iPadOS 26.1)
Hi everyone, I’m currently facing a blocking issue during App Review, and I’d really appreciate some help from anyone who has experienced something similar. My app was rejected under Guideline 2.1 – App Completeness with the following message: “An error message appeared after trying to Sign in with Apple. Device: iPad Air (5th generation), iPadOS 26.1.” The problem is: I cannot reproduce this bug at all, even when testing under the same conditions. ✔ What I tested: Physical iPad Air M2 on iPadOS 26.1 Physical iPhone devices iOS/iPadOS simulators (latest Xcode) TestFlight build (clean install) Debug build installed via Xcode (device connected) In every case, Sign in with Apple works correctly: Authentication sheet displays properly Callback returns the credential User is created/logged in without error No crash, no rejected promise, no empty credential ✔ Environment Using ASAuthorizationAppleIDProvider + ASAuthorizationController Default Apple Sign In button No custom nonce/redirect modifications No b
Replies
1
Boosts
0
Views
186
Activity
Nov ’25
LLVM Linker Crash on ARM64 with bfloat16 Symbols (Xcode 17.0.0)
LLVM Linker Crash on ARM64 with bfloat16 Symbols (Xcode 17.0.0) We're encountering a critical linker crash in Xcode 17.0.0 (clang-1700.4.4.1) on macOS 15.1.0 (Darwin 25.1.0) with Apple Silicon M3 Max when linking a pybind11 C++ extension against the MLX framework (v0.30.1). The linker consistently crashes with LLVM ERROR: No way to correctly truncate anything but float to bfloat during the linking phase, even though our code uses only integer types (int64, uint32) for BPE tokenization and never directly references bfloat16 types. Error Details: [100%] Linking CXX shared module _metal_trainer.cpython-312-darwin.so LLVM ERROR: No way to correctly truncate anything but float to bfloat clang++: error: unable to execute command: Abort trap: 6 clang++: error: linker command failed due to signal (use -v to see invocation) Reproduction: Install MLX framework: pip install mlx (any version with bfloat16 support) Create a minimal pybind11 extension that links against MLX: Compiler: AppleClang
Replies
1
Boosts
0
Views
211
Activity
Nov ’25
Reply to DEXT (IOUserSCSIParallelInterfaceController): Direct I/O Succeeds, but Buffered I/O Fails with Data Corruption on Large File Copies
Hi Kevin, Regarding your previous analysis of the KEXT configuration, specifically where you pointed out the IOMaximumByteCount is actually 0x80000 (512KB) in this post. We observed the runtime logs of the legacy KEXT, and the results align perfectly with your observation. Even when copying a 2GB file, the KEXT actually splits the request into 512KB (0x80000) chunks per transfer. [ProcessParallelTask] [KEXT_CHECK] WRITE (0x2a) | T:0 L:0 | Size: 524288 bytes (512 KB) This confirms that our current 1MB limit in the DEXT actually exceeds the behavior of the legacy driver. Since the current setting has passed all data integrity verifications, we consider the transfer size issue resolved and will not pursue larger transfer sizes at this stage. As per your recommendation, we are currently implementing the UserProcessBundledParallelTasks architecture to strictly follow DriverKit best practices and optimize performance (it is currently causing the DEXT to crash, so we are in the middle of debugging it). Than
Topic: App & System Services SubTopic: Drivers Tags:
Replies
Boosts
Views
Activity
Nov ’25
crash while exectuing __llvm_profile_write_file() in Xcode26.0
I am developing an iOS in-app SDK for collecting code coverage data. The SDK writes coverage data to a specified file by calling __llvm_profile_set_filename and __llvm_profile_write_file. This implementation worked correctly until I switched to Xcode 26.0 to build my project. Now, when __llvm_profile_write_file() is executed, it crashes with the following error stack. Can anyone provide any assistance? Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Subtype: KERN_INVALID_ADDRESS at 0x0000000000000001 Exception Codes: 0x0000000000000001, 0x0000000000000001 Termination Reason: Namespace SIGNAL, Code 11, Segmentation fault: 11 Terminating Process: exc handler [454] Thread 96 name: Dispatch queue: com.test-coverage.processing Thread 96: Crashed: 0 Demo 0x122602ea8 initializeValueProfRuntimeRecord (in Demo) (InstrProfilingValue.c:351) 1 Demo 0x00000001226064c0 writeOneValueProfData (in Demo) (InstrProfilingWriter.c:153) 2 Demo 0x0000000122606308 writeValueProfData (in Demo) (InstrProfilingWrit
Replies
0
Boosts
0
Views
262
Activity
Nov ’25
DeclaredAgeRange framework new cases and properties cause runtime crash with missing symbol
I'm making a wrapper library to abstract away some of the 'missing platform support' of DeclaredAgeRange until hopefully it expands to additional platforms. When I'm trying to fully enumerate all of the cases of AgeRangeDeclaration, which they all state available starting 26.0 (mysteriously added in Xcode 26.2 beta), the app crashes due to a missing symbol at launch time. This happens both for Xcode 26.1, 26.2 beta 2, and matching Xcode Cloud builds. So I've isolated it beyond doesn't work on my machine. I just made a handful of crashes and attached a sysdiagnose to a fresh feedback. FB21121092 - DeclaredAgeRange: Eligibility property and new declaration cases unavailable on iOS 26.1 device contradicting documentation - causes runtime symbol not found crash If anyone is curious what these crashes look like I've attached the DiagnosticPayload.jsonRepresentation() generated from one of my favorite frameworks, MetricKit. Very clearly articulated in the diagnostic metadata you
Replies
5
Boosts
0
Views
1k
Activity
Nov ’25
Reply to Lock Contention in APFS/Kernel?
So I guess I'm wondering: is it... fine to now use fdatasync on APFS? Because if it is now fine (as per sqlite's understanding via the Hacker News comment...), then I think there's a bunch of software might be relying on outdated documentation/advice, since: So, the first thing to understand is that what led to F_FULLFSYNC wasn't really the kernel itself's handling of data. The basic issue was that the kernel itself would send the data all the way to disk... and which point the drive itself would stick the data in a write cache and leave it there for an indeterminate but long time. Even worse: Some of these drives were intentionally ignoring the existing commands (and more performant) that were supposed to flush the specific data. These issue were widespread enough across product and vendors that blaming hardware wasn't really feasible. The only solution we found viable was what F_FULLFSYNC does, which is to flush the data and the force the drive to commit the data. I'll also note that issue above was never s
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Nov ’25
Reply to Age Range API - Sandbox Testing Available
Using Xcode 26.2, targeting an iPhone 17 Pro running 26.1, Xcode crashes saying the symbol isn't available. The isEligibleForAgeFeatures property is actually available in iOS 26.2 beta or later. The documentation showing it as iOS 26 is a bug. Thank you for filing your Feedback report. Upgrade your device to iOS 26.2 beta to test it.
Topic: App & System Services SubTopic: General Tags:
Replies
Boosts
Views
Activity
Nov ’25
Reply to Persistent font registration crashes when fonts are delivered via Apple-Hosted Background Assets
Hi Quinn, Thank you for the detailed analysis — especially the breakdown of the crashing thread and explanation about the Swift concurrency actor expectation. That was extremely helpful. I tested your suggestion: CTFontManagerRegisterFontURLs(cfArray, scope, true) { @Sendable _, _ in true } Result This does prevent the crash. The system “Install Fonts” sheet appears, and tapping Install no longer triggers a trap. Remaining Issue Although the crash is fixed, the fonts still do not install system-wide when using the .persistent scope with fonts delivered via Apple-Hosted Background Assets. After tapping Install, nothing appears under: Settings → General → Fonts → My Fonts So the concurrency crash is resolved, but the underlying issue remains: .process registration works .persistent registration does not install fonts No errors are returned by CTFontManagerRegisterFontURLs Next Steps As you suggested, I am happy to have FB21109320 repurposed to track the missing concurrency an
Replies
Boosts
Views
Activity
Nov ’25
Reply to SwiftData not loading under iOS 26.1
Hello again, So, they are two issues. The crash and the iCloud sync dealing with this new @Attribute trasformables that Apple change for us and thus, provoking this mess. In all honestly, Apple is the one that should be making the Tweaks, not us. In-memory models should respect the existing data store of our Apps since they are already being used by thousands of users in realtime. Someone above probably doesn't want to deal with the iOS26.2 publishing date (it's in the final stages) and that is the wrong decision. Why do we have to clean the mess when Apple made our code incompatible? 😒. Makes no sense. ** ** Are you aware how many weeks of work it will take for us to refactor all of our Apps using this confusing tweak with decodables? Sorry but your solution is not acceptable.
Replies
Boosts
Views
Activity
Nov ’25