As of the latest available information, Apple does not directly provide an endpoint for checking refund history for multiple transactions in a single request via their App Store Server API. The endpoint
https://api.storekit.itunes.apple.com/inApps/v2/refund/lookup/{transactionId}
allows you to check the refund status for a single transaction ID at a time. What if you have 8000 subscribers? Are we going to send 8k requests everyday? What's the solution for this scenario? We don't want to implement the notifications by the way. Any solutions?
Post
Replies
Boosts
Views
Activity
I updated my Xcode to 15.3 and updated the operating system to Sonoma 14.4 yesterday. Now Xcode cannot launch the app. I deleted it, restarted the MacBook Pro M1, deleted the derived data etc. Nope, the working and launching iOS app isn't launch anymore. How to fix this issue? The patch destroyed my Xcode. Any solution I am seeing the following:
(5517) MallocStackLogging: could not tag MSL-related memory as no_footprint, so those pages will be included in process footprint - (null)
The iPhone is only showing a black screen. The app cannot launch. Thanks.
My Xcode is crashing in every 20 - 30 minutes with no reason. The crashes started after I installed macOS Venture 13.0.1 (22A400). I have been sending crash reports to Apple but no response. I can't do development and losing my saved data. That's the crash reason:
Crashed Thread: 15 Dispatch queue: DVTSourceControlGitXPCClient :: Proxy Completion Queue
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x00000002d83bffe0
Exception Codes: 0x0000000000000002, 0x00000002d83bffe0
Termination Reason: Namespace SIGNAL, Code 10 Bus error: 10
Terminating Process: exc handler [75986]
Any idea how to take Apple's attention to force them release an urgent patch for this issue? My laptop is Apple M1 Max and all the other developers in my team having the same issue.
When I run the Profile in Xcode I released that JSONDecoder causing memory leak? The following is the code snippet where the memory leak happens:
if let data = try? JSONSerialization.data(withJSONObject: dict, options: []) {
let decoder = JSONDecoder()
if let decodedObj = try? decoder.decode(T.self, from: data) {
value = decodedObj
}
}
It is a generic class and I believe T isn't causing this. I googled the problem and saw too many issues about memory leak with JSONDecoder of other developers.
try autoreleasepool {
....
}
didn't work.
Have you tried generic functions with JSONDecoder().decode? It seems Swift5 didn't solve the memory leak issue in JSONDecoder.