missing package product

[quote='796464022, ingconti, /thread/691407?answerId=796464022#796464022, /profile/ingconti'] is better to use a TSI?? [/quote] DTS tech support incidents (TSIs) have been replaced by code-level support request and, as part of that process, DTS has switched to doing the bulk of our work on DevForums. There are three common file extensions for crash reports: .txt .ips .crash I’ll cover each in turn. Additionally, there is a lot of useful info in the various docs linked to by Diagnosing issues using crash reports and device logs. The first (.txt) isn’t ideal. You see it in places where the system requires a text file, like here on DevForums (see Posting a Crash Report) and in reports from App Review. If you get a .txt file, open it with a text editor to see what the real format is, and then change the extension to either .crash or .ips. The second format (.ips) is used for JSON crash reports. This is easy to identify because it looks like JSON. For example: {app_name:Xcode,…} { uptime : 1400000, … } IMPORTANT I

Problem solved. When compared to another project I’m working on, I noticed something missing from the “Signing & Capabilities” under macOS App Sandbox… Once I checked Outgoing Connections (Client), Xcode created a new entitlements file (oddly named AppNameDebug.entitlements) and added the setting Outgoing Network Connections = YES. Following my next build and run, sync to CloudKit databases worked perfectly. Can’t figure why this wasn’t required before. I didn't uncheck this and the previous entitlements file did not contain this line item before. All I can suggest is that I added an #if DEBUG macro to my project around the same time, so maybe this triggered the requirement? #if DEBUG do { // Use the container to initialize the development schema. try container.initializeCloudKitSchema(options: []) } catch { // Handle any errors. } #endif But main problem solved. If anyone has an explanation that would be appreciated.

I 've managed to start my app now i can see the following crash report information: Termination Reason: Namespace DYLD, Code 1 Library missing Library not loaded: @loader_path/libsteam_api.dylib Referenced from: <......B-3DDF-3AD6-B3C8-C39C3771A824> /Applications/WattAttack-Mac-Shipping.app/Contents/MacOS/WattAttack-Mac-Shipping Reason: tried: '/Applications/WattAttack-Mac-Shipping.app/Contents/MacOS/libsteam_api.dylib' (code signature invalid in <.......-0547-37ED-844E-89C9CABACBCA> '/Applications/WattAttack-Mac-Shipping.app/Contents/MacOS/libsteam_api.dylib' (errno=1) sliceOffset=0x00004000, codeBlobOffset=0x00027B70, codeBlobSize=0x000055F0) (terminated at launch; ignore backtrace) I've read different articles related to this code signing error but cant figure out how to fix the problem :(

OK. Did you look at the logs that Xcode generates when you export? I suspect you’ll see that it’s not passing the right values for --preserve-metadata. Regardless, you should file a bug against Xcode here. Please post your bug number, just for the record. As to the workaround, you’ll have to manually export your code from your Xcode archive. See Creating distribution-signed code for macOS, starting at the Export a non-app product built with Xcode section. Note that this isn’t as tricky than it might seem because you can follow the trail blazed by Xcode: Export using Xcode. Look in the logs to see what Xcode did. Apply the minor tweak to the --preserve-metadata option. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Something that could potentially be considered a workaround would be to set the synthesizers usesApplicationAudioSession to false, while also having the app itself activate/deactivate the audio session before and after using the AVSpeechSynthesizer. Essentially wrapping all usage of the synthesizer that no longer uses the apps audio session within an explicit app audio session. In my testing this appears to have the desired AVAudioSession settings kick in and there are no exceptions thrown. BUT, that then causes the UI to pause updates both when activating and de-activating the session, which is a worse outcome (in current example it only pauses when de-activating). If I have missed a way to not have activating/deactivating the audio session pause UI updates, which you could point me to, I could utilize this workaround.

Looks like the version of Python matters. My environment: MacBook Pro 14-inch, 2021, M1 Pro, 16 GB Using this code example I've created two different virtual environments: Python 3.8.19 Python 3.11.9 Results Python 3.8 (CPU) Epoch 1/5 782/782 [==============================] - 403s 513ms/step - loss: 4.8157 - accuracy: 0.0648 Python 3.8 (GPU) Epoch 1/5 2024-07-22 21:35:48.809586: I tensorflow/core/grappler/optimizers/custom_graph_optimizer_registry.cc:114] Plugin optimizer for device_type GPU is enabled. 782/782 [==============================] - 64s 77ms/step - loss: 4.9219 - accuracy: 0.0574 Python 3.11 (CPU) Epoch 1/5 782/782 ━━━━━━━━━━━━━━━━━━━━ 435s 544ms/step - accuracy: 0.0480 - loss: 5.0793 Python 3.11 (GPU) Epoch 1/5 2024-07-22 21:48:42.497240: I tensorflow/core/grappler/optimizers/custom_graph_optimizer_registry.cc:117] Plugin optimizer for device_type GPU is enabled. 782/782 ━━━━━━━━━━━━━━━━━━━━ 412s 472ms/step - accuracy: 0.0487 - loss: 5.1804 I did not include

Hi @Reon, You wrote: [...] We are using the C# BouncyCastle Dotnet package to handle the EllipticCurve decryption. Apple does not support third-party libraries or services, so I'd advise you to contact the support channels for BouncyCastle directly. However, I will provide some guidance based on some commonly known issues regarding .NET decryption below. Then, you wrote: [...] We find on average that about 2% of all our deposits are failing because the library fails to decrypt the ApplePay SDK Data payload with the error: Mac check in GCM failed. [...] This low rate of failure may be partially due to a race condition if your encryption/decryption processes are configured in a multithreaded environment. Although rare, one potential failure point is during the auth handshake. One way to troubleshoot this locally is to perform the handshake and decryption on a single thread and process. This should factor out any issues related to corrupted data or unpaired handshakes due to race conditions or poor net

Hi @Ddud, You wrote: [...] Furthermore, my logs show that I am successfully sending my notification to APN, so it is confusing that no notification appears on my phone. [...] Before we begin, I'd like to confirm that you've read the following documentation: Adding a Web Service to Update Passes Register a Pass for Update Notifications Send an Updated Pass To send a pass update push notification, perform the following steps: Find the registered devices for the updated pass. Create and send a push notification for each registered device. Verify your notification matches the following criteria: Uses the same certificate and private key that the creator of the original used for signing. The push token registered by the device. Contains an empty JSON dictionary for the notification payload. For invalid push token errors, delete the associated device from APNs. For more information, see Sending notification requests to APNs. Next, you wrote: [...] token: { [...] } [...] Please remove sensitive information from your

It can be multiple things. Make sure you're comparing apples to apples: there are multiple metrics for installs and you also have multiple dimensions (country, apps, device, product page, source, etc). More often than not, that's the actual problem. I'd review my data closely and look at their docs to make sure you're looking at the same thing. Privacy thresholds: this could be it indeed. What you can do here is to avoid the Detailed report if your app is too small. I hope this is helpful.