After upload using transporter I get following message:
"Cannot be used with TestFlight because the signature for the bundle at “GSequencer.app” is missing an application identifier but has an application identifier in the provisioning profile for the bundle. Bundles with application identifiers in the provisioning profile are expected to have the same identifier signed into the bundle in order to be eligible for TestFlight." (90886)
I am unsure about the cause of this problem, please give some advice howto fix?
Hi,
it seems like the wachOS sysdiagnose debug profile is no longer valid and needs to be updated. Any idea to whom we should reach out to get this fixed?
I am talking about the profile linked here:
https://developer.apple.com/bug-reporting/profiles-and-logs/?platform=watchos
Kind regards
Alex
I've reached a point where I can no longer make any progress diagnosing the issues that have popped up with Apple Watch development support. To hopefully help draw attention and focus to the severity of this problem, I'm gathering all related threads into this single thread.
Summary of problems
There are several, possibly related, issues at play:
Xcode is not discovering Apple Watches. This means it's not possible to deploy apps to Apple Watches that aren't already provisioned with Xcode. I've confirmed this behavior with a watch running watchOS 10.0.
The logging profile for watchOS has expired. It's no longer possible to pull logs via Console from Apple Watches.
AppIntent-based complications on watchOS 10.5 no longer load, staying stuck in a "placeholder" state. This can be reproduced with the Backyard Birds demo app.
It's no longer possible to debug widget extensions on Apple Watch hardware.
Feedback submitted
FB13758427: No longer able to connect to Apple Watch from Xcode
I was attempting to test another regression related to AppIntents no longer working on watchOS 10.5. To confirm the behavior had regressed since earlier versions of watchOS, I set up one of my older Apple Watches that is still running watchOS 10.0.
After wiping the watch and repairing it with one of my test devices (iPhone 11 Pro, iOS 17.4.1), I’m unable to get the Apple Watch to appear in Xcode’s Devices & Simulators manager. The phone is connected via USB cable, and the phone appears as a Connected phone, but the watch does not appear. My Apple Watch Ultra that I use as my daily driver does appear as a remote device (the globe icon is next to it), but the Apple Watch 10.0 does not appear.
Details about the older watch:
Version: 10.0 21R5341c
Model: A2478
Not being able to test on other Apple Watches is severely limiting my ability to isolate and confirm the regression in AppIntent support that can be reproduced in the Backyard Birds demo app.
Note that the 10.0 watch does actually appear in the Console app, but with a warning sign next to it. The 10.0 watch also appears twice. Clicking the warning sign does not reveal any information about why the warning is appearing, but after ~5 seconds I do get the following error in Console.app: “The user has not responded to the pairing request on 'Headless’ Respond to the Trust prompt on the device.” There is no trust prompt on the device.
FB13756074: WatchOS logging profile is no longer valid
https://developer.apple.com/bug-reporting/profiles-and-logs/?platform=watchos is no longer valid. See attached error that occurs when attempting to install the profile onto my Apple Watch Ultra.
It seems that without this I’m unable to get any logs off of my Apple Watch, which is making testing/development quite difficult.
FB13758450: AppIntent-based widgets no longer render on watchOS 10.5
AppIntent-based complications no longer get beyond a placeholder state on watchOS. This can be reproduced with the Backyard Birds demo app, which uses AppIntent-based widget configurations for the watchOS complications. AppIntent-based complications did appear to work in previous versions of watchOS 10, but I’m unable to confirm this with a 10.0 Watch I have due to FB13758427.
To reproduce
deploy the attached unmodified Backyard Birds app to a watch running watchOS 10.5.
add a Backyard Birds complication to a watch face.
Expected behavior: the widget shows live data
Actual behavior: the complication never leaves a placeholder state. See the attached screenshot for the state the widget is stuck in.
FB13758490: PacketLogger no longer logs packets
PacketLogger used to log BTLE packets as they were received and transmitted on a macOS machine. Since updating to 14.5 Beta (23F5064f) however, PacketLogger no longer logs packets on macOS at all. Upon starting a new session, the interface remains empty.
PacketLogger is still able to log packets from a connected iOS device.
Related threads
Apple Watch cannot reconnect
WatchOS Sysdiagnose Profile is no longer
XCode 15 can't run on iOS 17 devices. Previous preparation error: An error occurred while communicating with a remote process.. The connection was invalidated.
We have a legacy app written in a mix of C, ObjC, C++ and ObjC++ with .xib files. It is not sandboxed.
It sends an Apple Event to TV (the app of that name from Apple, not a physical TV) using /usr/bin/osascript, calling a compiled Apple Script which is in our app bundle's Resources directory with parameters which we generate in our app at runtime. The first time it does this on a fresh system, the OS puts up a dialog asking for permission to control TV, and after the user clicks Allow, our app appears under Security and Privacy in the Automation section.
That's all fine, but what is unexpected is that the app has no Apple Events entitlement (com.apple.security.automation.apple-events), and it doesn't have a NSAppleEventsUsageDescription string either. The documentation at https://developer.apple.com/documentation/bundleresources/entitlements/com_apple_security_automation_apple-events says
Your app doesn’t need the Apple Events Entitlement if it only sends Apple events to itself or to other processes signed with the same team ID.
but we're not on the Apple team.
When I filter the log for messages from tccd pertaining to our app, it does indeed complain :
Prompting policy for hardened runtime; service: kTCCServiceAppleEvents requires entitlement com.apple.security.automation.apple-events but it is missing for accessing={TCCDProcess: identifier=<our bundle id>”
But despite those complaints, everything works - I can send the event, and TV acts upon it. Is this working only by accident, and might fail in some minor future OS update?
tccd also complains about the microphone
Prompting policy for hardened runtime; service: kTCCServiceMicrophone requires entitlement com.apple.security.device.audio-input but it is missing for requesting={TCCDProcess: identifier=<our bundle ID>
but we don't use the microphone
tccd complains about this too
<path-to-our-app> attempted to call TCCAccessRequest for kTCCServiceAccessibility without the recommended com.apple.private.tcc.manager.check-by-audit-token entitlement
What does that mean, and should we be concerned?
Hi,
I have codesigned my application and after this macos won't run the binary anymore.
codesign -f -o runtime --timestamp -s "Developer ID Application: YOUR NAME (TEAM_ID)" --entitlements $HOME/workspace/GSequencer-cocoa/gsequencer-macos/macos-contrib/GSequencer.entitlements -i com.gsequencer.GSequencer --deep $HOME/workspace/GSequencer-cocoa/gsequencer-macos/build/universal/GSequencer.app
Verify signature works.
codesign -vv $HOME/workspace/GSequencer-cocoa/gsequencer-macos/build/universal/GSequencer.app
The same for the DMG file, still doesn't work anymore.
codesign -f -o runtime --timestamp -s "Developer ID Application: YOUR NAME (TEAM_ID)" $HOME/workspace/GSequencer-cocoa/gsequencer-macos/build/arm64/GSequencer-6.9.1.dmg
I would love to distribute my application with code signing. Note all libraries are built using clang or clang++.
I figured out that when I leave entitlements away it would launch but complains about library signatures.
regards, Joël
None of my existing apps (both in-AppStore and in-development) nor even a brand new WatchOS app can be installed to my Apple Watch. While using Xcode to build and deploy to my Watch, I get this:
”Waiting to reconnect to Apple Watch
Xcode will continue when the operation completes.”
However, this dialog persists and never completes.
I’m running all of the latest: MacOS 14 beta 4, Xcode 15 beta 5, Watch OS 10 beta 4, iOS 17 beta 4.
I’ve tried resetting my Watch (with “Erase All” option) and restarting the Mac, the phone and the watch.
Any help?
Hello,
I recently ran a virus/malware scan on my dev machine using ClamAV, this was run via macOS Terminal using the 'clamscan' function.
Everything came back okay except a keylogger in the ProVideo Framework for physical iOS Test Devices. Please see below for 'clamscan' output:
/Users/username/Library/Developer/Xcode/iOS DeviceSupport/iPad8,11 17.4 (21E219)/Symbols/System/Library/PrivateFrameworks/ProVideo.framework/ProVideo: Unix.Keylogger.Macos-10023932-0 FOUND
My understanding is that '/Library/Developer/Xcode/iOS DeviceSupport/' is where Xcode keeps the files related to physical test devices that are required for debug. There were 3 Instances of this keylogger, all of which corresponded to physical devices I own and iOS Versions that I have installed / were installed.
Can anyone verify if 'Unix.Keylogger.Macos-10023932-0' is a valid file that ClamAV is incorrectly detecting as malicious?
If it is a valid debug file provided by Apple, it seems strange that it's located in the ProVideo Framework. I couldn't find any documentation online about this so any information would be appreciated.
At this stage I have deleted the contents of '/Library/Developer/Xcode/iOS DeviceSupport/', my understanding is that these symbols are only transferred to the system when I test software via Xcode on a physical device and will not reproduce until I do that again. To me it's unclear if perhaps this keylogger is present on my iOS Device and is being transferred to the Mac via Xcode? Or somehow it is just appearing in this folder?
Thanks!
Hi,
So recently I've been itching to get some actual work done and create something that is genuinely useful to me. Mainly, I want to practice my skills and hopefully build up some new ones.
My concept/idea is to create something that resembles spatial audio ( or spatialized stereo ), but on steroids for macOS. I want to create something that has much more customizability, but also ease of use. I'd like to make use of the power in products like AirPods Pro and create a more immersive audio experience. However, before I make any serious plans, I'd like to ask for some feedback, really just to consider the feasibility of something like this. I throughly enjoy a rich audio experience, but I feel the experience as is on macOS is quite lackluster, especially compared to iOS with system wide spatialized stereo already available.
I would genuinely appreciate any feedback or support that could be given on this project. Thank you for your time.
I also apologize if this is the wrong usage of this forum/support.
This app or its metadata appears to be misrepresenting itself as another popular app or game already available on the App Store, from a developer's website or distribution source, or from a third-party platform.
Apps should be unique and should not attempt to deceive users into thinking they are downloading something they are not....
For the past four years, my app has been live on the Play Store and is also accessible on several other platforms. Despite this, my attempts to publish it on the App Store have been consistently rejected citing Guideline 4.1 - Design - Copycats. Apple has not specified the exact proof of rights they are looking for. To address this, I have recorded my personal Google Play Developer Console account to showcase that I possess all the required rights to manage the app on Google Play. I am seeking advice on the best course of action to resolve this issue.
I am developing an app in mixed immersive native app on Vision Pro. In my RealityView, I add my scene by content.add(mainGameScene). Normally the anchored position (original coord) should be the device position but on the ground (with y == 0 on the ground). At least this is how I understand the RealityViewContent works. So if I place something at position (0, 0, -1.0), the object should be in the front of you but on the floor (z axis is pointing backwards)
However recently I load a different scene and I add that with same code, content.add(mainGameScene), something has changed, my scene randomly anchored on the floor or ceiling, according to the places I stand or sit. When I open Visualizations of my anchoring point, I could see that anchor point I am using is on the ceiling. The correct one (around my foots) is left over there.
How could I switch to the correct anchored position? Or does any setting can change the behavior of default RealityViewContent?
I am able to successfully install the app on my device, but I am unable to verify the app.
Steps to reproduce:
Navigate to Settings -> VPN & Device Management on iPhone 14
Select developer under Developer App
Select trust this computer
Attempt to Verify App
The "Verify App" button has no effect. The app can still be installed when built, but is not able to be opened. Navigating to ppq.apple.com in a browser results in a "cannot be trusted":
Hi,
I am having this rare issues, where a handful of my users are crashing when trying to access their realm file. This is the error I'm seeing:
Fatal error: 'try!' expression unexpectedly raised an error: Error Domain=io.realm Code=3 "Failed to open file at path '/var/mobile/Containers/Data/Application/BCA5E4BC-5923-4D7E-8142-AB49B32A7E59/Documents/default.realm.lock': Operation not permitted" UserInfo={Error Code=3, NSFilePath=/var/mobile/Containers/Data/Application/BCA5E4BC-5923-4D7E-8142-AB49B32A7E59/Documents/default.realm.lock, Error Name=PermissionDenied, NSLocalizedDescription=Failed to open file at path '/var/mobile/Containers/Data/Application/BCA5E4BC-5923-4D7E-8142-AB49B32A7E59/Documents/default.realm.lock': Operation not permitted}
and I can report that for all for those users, it seems that identiferForVendor has returned nil. So it looks like that's the common denominator.
Any idea on what other data I can log or what's the issue here?
Thanks..!
Hi, so I have looked through a lot of the Arduino forums and some of which have been helpful and others not so much. I am trying to transfer data from my arduino uno r4 wifi to my xcode project through my HM-10 XC4382 BLE Bluetooth Module. I am trying to essentially scan an RFID tag and transmit the name and UUID to the phone app to acknowledge the tag has been scanned.
Every time I connect to my HM-10 module successfully on my phone but when I try and print the message it shows up as empty. When trying to debug it does show the statement when I scan the RFID tag each time which tells me it is being received but perhaps the format is not compatible with Xcode? Would appreciate any assistance 🙂
I have both arduino code and swift code. In my arduino code, I am working with RFID Scanner (from Jaycar) using the MFRC522 library and is connected the following ways:
Apologies if I may have missed some code / context to this question. Thank you!
RFID Module Setup
3.3V - 3.3V
RST - 9
GND - GND
MISO - 12
MOSI - 11
SCK - 13
SDA - 10
HM-10 Setup
5V - 5V
GND - GND
RX - TX (arduino)
TX - RX (arduino)
Find code attached in text files.
ArduinoCode.rtf
SwiftCode.rtf
My safari plugin login verification is based on cookies. I found that as long as the plugin is used for a period of time, refreshing the page and making another request will result in the loss of cookies. I want to know if there are any other ways besides changing the login verification method to bypass cookies?
In my sandboxed MacOS app I want to access OSLogStore programmatically to fetch logs for multi-component application (app, libraries, deriver) for further analysis. According to the documentation, - https://developer.apple.com/documentation/oslog/oslogstore/3366102-local the app should have com.apple.logging.local-storeentitlement.
I have added this entitlement "by hand" to the entitlement file as I I can't find a correspondent entry in the Xcode -> Sign & Capabilities interface.
When I run the app, I get Unsatisfied entitlements: com.apple.logging.local-store error and the app doesn't start.
If I remove the entitlement, the app can't get access to the logd subsystem.
How can I add com.apple.logging.local-store to my app?
Should I request this not visible via Xcode configuration UI from apple?
Thanks!
We’ve observed a couple of concerning alterations in the passkey registration and authentication behaviour in iOS 17.4.1:
During passkey registration, “excludeCredentials” property is ignored. Existing passkey is silently overwritten and no error is reported from navigator.credentials.create (both, Safari and Chrome).
However, according to W3 spec when “excludeCredentials” is present in the PublicKeyCredentialCreationOptions -
“The client is requested to return an error if the new credential would be created on an authenticator that also contains one of the credentials enumerated in this parameter.”
PublicKeyCredentialCreationOptions we use:
"credCreateOptions": {
"rp": {
"name": "RP name"
},
"user": {
"name": "username",
"id": "abcd"
},
"challenge": "56elsKE5pKgEECg-fJpLl3gF33ACRSVBl00Mn03JAIk",
"pubKeyCredParams": [
{
"type": "public-key",
"alg": -7
}
],
"excludeCredentials": [
{
"type": "public-key",
"id": “abcd”
}
],
"authenticatorSelection": {
"authenticatorAttachment": "platform",
"userVerification": "required"
},
"hints": [
"client-device"
],
"attestation": "direct",
"extensions": null
}
}
This behaviour is different from what is observed on iOS 17.3.1 where the registration call to navigator.credentials.create with the same options produces the following error: “At least one credential matches an entry of the excludeCredentials list in the platform attached authenticator”
During passkey login flow, iOS 17.4.1 ignores
"hints": [ "client-device" ]
According to https://developer.mozilla.org/en-US/docs/Web/API/CredentialsContainer/create#client-device, hints specify what authentication UI the user-agent should provide for the user. “client-device” requests the user authenticates using their own device, such as a phone.
Here’s our PublicKeyCredentialRequestOption:
"credRequestOptions": {
"challenge": "xk_wd1BaVue7mOZ-UM_KVj6Z4AmGxf12_7H1Gilq01I",
"timeout": 300000,
"allowCredentials": [
{
"type": "public-key",
"id": “abcd”,
"transports": [
"internal"
]
}
],
"userVerification": "required",
"hints": [
"client-device"
],
"extensions": null
}
}
However, iOS 17.4.1 gives user an option to sign in with another device .
On iOS 17.3.1, the request to navigator.credentials.get with the same same PublicKeyCredentialRequestOption presents the UI screen without the “Sign In with Another Device” option.
Is that a bug on iOS 17.4.1 or intended behaviour? This does not follow the official specs and different from the other platforms like Android.
Is there any documentation around this change on iOS 17.4.1? That would be helpful.
In Big Sur when I use window.toolbarStyle = NSWindowToolbarStylePreference and set toolbar.displayMode = NSToolbarDisplayModeIconAndLabel the toolbar buttons don't take on the Preferences style.
The hover and click state is only over the icon when it should be a large box surrounding the icon and label. These are the normal toolbar button styles. How do I get the buttons to take on the Preferences style?
I've had to resort to using window.contentViewController = NSTabViewController to get the right toolbar button style.
Is there something special I need to do to get NSWindowToolbarStylePreference to work?
I'm adding AppIntents to my existing "ShopList" app and I'm having two problems that I think are related.
I can't get shortcuts (or Siri) to work when I pass a parameter to an intent. It works if I don't pass a parameter though.
My StoreEntityQuery.suggestedEntities function is not being called during initialization.
I have an AppIntentsShortcutProvider defined as follows.
class ShopListShortcuts: AppShortcutsProvider {
static var appShortcuts: [AppShortcut] {
AppShortcut(intent: FindStore(), phrases: [
"Find \(\.$store) store in \(.applicationName)"
],
shortTitle: "Find Store",
systemImageName: "cart")
}
}
Details below. I would appreciate any suggestions on what I'm missing or doing wrong.
In my AppDelegate "didFinishLaunchingWithOptions" function, I call ShopListShortcuts.updateShortcutParameters.
The FindStore struct is defined as follows.
struct FindStore: AppIntent {
static var title: LocalizedStringResource = "Find Store"
static var description = IntentDescription("Finds a store.")
static var openAppWhenRun: Bool = false
@Parameter(title: "Store", description: "The store.")
var store: StoreEntity
@MainActor
func perform() async throws -> some IntentResult {
print("performing intent with \(store.id) and \(store.name)")
return .result()
}
}
The StoreEntity is defined as follows.
struct StoreEntity: AppEntity {
...
static var defaultQuery = StoreEntityQuery()
var id: Store.ID
@Property(title: "Store Name")
var name: String
...
}
And finally the StoreEntityQuery is defined as follows.
struct StoreEntityQuery: EntityQuery {
func entities(for identifiers: [StoreEntity.ID]) async throws -> [StoreEntity] {
print("entities call")
return ...
}
func suggestedEntities(for identifiers: [StoreEntity.ID]) async throws -> [StoreEntity] {
print("suggested entities call")
return ...
}
}
billnbell.
