Search results for

“Visual Studio Maui IOS”

109,098 results found

Post

Replies

Boosts

Views

Activity

CloudKit: Efficient way to get user's rank in leaderboard without fetching all records?
CloudKit: Efficient way to get user's rank in leaderboard without fetching all records? I'm building a leaderboard feature using CloudKit's public database and need advice on the best approach to calculate a user's rank efficiently. Current Setup Record Structure: Record Type: LeaderboardScore Fields: period (String): daily, weekly, monthly, allTime score (Int): User's score profile (Reference): Link to user's profile achievedAt (Date): Timestamp Leaderboard Display: Initially fetch first 15 users (sorted by score descending) Paginate to load more as user scrolls Show total player count Show current user's rank (even if not in top 15) The Challenge I can fetch the first 15 users easily with a sorted query, but I need to display the current user's rank regardless of their position. For example: User could be ranked #1 (in top 15) ✅ Easy User could be ranked #247 (not in top 15) ❌ How to get this efficiently? My Current Approach Query records with scores higher than the user's score and count them: // Count how
3
0
146
2w
Reply to Direction data not available with U2 chip (iPhone 15 Pro and iPhone 16 Pro) when using Murata SR040/SR150 accessory
Having a similar problem, although I'm not sure if it's related to iOS26 or phones with the U2 chip. I am doing peer to peer rather then peer to object, but figured I'd share my findings. iPhone 16 Pro (U2 chip), iOS 26.3.1: NISession created — capabilities: token: true supportsDirection: false supportsCameraAssistance: true supportsExtendedDistanceMeasurement: true supportsPreciseDistanceMeasurement: true iPhone 12 (U1 chip), iOS 18.6.2: NISession created — capabilities: token: true supportsDirection: true supportsCameraAssistance: true supportsExtendedDistanceMeasurement: false supportsPreciseDistanceMeasurement: true What I've found so far: 16 Pro / U2 / iOS 26 (?) 3D direction vector is never available Camera seems to be required for directional convergence Everything seems to be determined by hAngle Seems to start an NI session with dirSrc as 'none' and then resolves to 'hAngle' after camera convergence is complete 12 / U1 / iOS 18 Seems to start an NI session with 'hA
2w
Reply to Nearby Interaction property supportsDirectionMeasurement returns false and NINearbyObject direction property is nil
Having the same problem, although I'm not sure if it's related to iOS26 or phones with the U2 chip. Worth noting that I am doing peer to peer rather then peer to object, but figured I'd share my findings. iPhone 16 Pro (U2 chip), iOS 26.3.1: NISession created — capabilities: token: true supportsDirection: false supportsCameraAssistance: true supportsExtendedDistanceMeasurement: true supportsPreciseDistanceMeasurement: true iPhone 12 (U1 chip), iOS 18.6.2: NISession created — capabilities: token: true supportsDirection: true supportsCameraAssistance: true supportsExtendedDistanceMeasurement: false supportsPreciseDistanceMeasurement: true What I've found so far, at least the case of the 16 Pro / U2 / iOS 26 (?): 3D direction vector is never available Camera seems to be required for directional convergence Everything seems to be determined by hAngle Placing both a 16 Pro and a 12 face down on a table with rear cameras covered: 12 continues to show position with a dirSrc of '3D'; 16 Pro
Topic: App & System Services SubTopic: General Tags:
2w
Reply to Recurring FigXPCUtilities / FigCaptureSourceRemote err=-17281 logs when using AVCaptureVideoDataOutput on iOS 26.x
Thanks for this interesting post! I'm not an expert on that field nor that API. Hope one of the engineers on that team can jump into this thread for better info. These specific FigXPCUtilities and FigCaptureSourceRemote logs are almost certainly benign internal framework noise rather than a regression or a flaw in your capture pipeline. Looking up the err=-17281 is a CoreMedia error code that, without knowing here, typically points to a minor XPC synchronization hiccup, a port invalidation, or an asynchronous state mismatch during the setup or teardown of the capture session? I believe this logs are for information only and should be removed. Code paths that silently recovered in older iOS versions often have their log levels elevated in newer releases (or beta releases), resulting in console spam. If your AVCaptureVideoDataOutputSampleBufferDelegate is successfully receiving CMSampleBuffer frames and your preview layer is rendering smoothly. You can safely ignore these logs. If you want to temporari
2w
not seeing In-App Purchase and Subscriptions
after doing all the steps as in The app version submission must be in the “Prepare for Submission” state There must be at least one IAP/subscription in the “Ready to Submit” state All banking & agreements must set up and in place I am still not seeing the In-App purchase and subscription in my iOS App Version page to add to my newest version slash build
1
0
62
2w
Reply to Recurring FigXPCUtilities / FigCaptureSourceRemote err=-17281 logs when using AVCaptureVideoDataOutput on iOS 26.x
Similar issue here when starting an ARSession. iOS 26.3.1 on an iPhone 16 Pro. No issues running the same app on an iPhone 12 on iOS 18.6.2 `(Fig) signalled err=-12710 at <>:601 <<<< FigXPCUtilities >>>> signalled err=-17281 at <>:308 <<<< FigCaptureSourceRemote >>>> Fig assert: err == 0 at bail (FigCaptureSourceRemote.m:569) - (err=-17281)`
2w
Developer account terminated for “feature switching” – need advice on reinstatement
Hey everyone, I’m looking for advice from anyone who’s been through something similar. My Apple Developer account was recently terminated due to what Apple described as “concept or feature switching.” After digging into it more, I believe this happened because I made updates to my app after it was approved without submitting a new version for review. Here’s what I changed: Added a new screen (friends list) that required navigation changes Updated parts of the UI (visual improvements) Added a feature (button that helps users structure a plan) Enabled Google sign-in I did not change payments, subscriptions, or the core purpose of the app. At the time, I didn’t fully understand that these kinds of changes (especially anything affecting navigation or features) need to go through a new App Store submission rather than being updated remotely. I now understand how Apple could see this as bypassing the review process. Since then, I’ve: Stopped all over-the-air/runtime updates Made sure the app matches the la
0
0
42
2w
Intermittent connectivity issues on iOS 26.4 Beta - Potential iCloud Private Relay conflict
I am investigating a connectivity issue reported by a user running latest iOS 26.4 Public Beta on an iPhone 17 Pro Max. Unfortunately, I am unable to reproduce this behavior on my end as I do not have access to an iPhone 17 Pro Max for testing, and my current devices do not exhibit the issue. However, the user's logs suggest a system-level networking issue : Symptoms: Flutter App (package dio): Requests fail with The connection errored: Failed host lookup: 'mydomain.com' Firebase SDK: Unable to fetch Firestore documents Duration: The outage is random, lasting between 5 to 15 minutes before self-resolving Scope: It affects both Wi-Fi and Cellular data By the way I found this report from another developer experiencing the exact same behavior: I run a mobile app that has millions of users. As of 1-2 weeks ago, we started getting reports that the app isn't working (failing to connect). It then goes back to connecting anywhere between 5 to 15-20 mins later. Every single one of those users was running iOS
1
0
173
2w
Reply to Bug: Wi-Fi Aware (NAN) Subscriber Mode: nwPath.availableInterfaces Does Not Include nan0 Interface After Successful Peer Connection
[quote='880225022, wu_aaron, /thread/818708?answerId=880225022#880225022, /profile/wu_aaron'] we need to establish multiple additional NWConnection instances … over the Wi‑Fi Aware network [/quote] I don’t think you can do this on currently shipping systems. However, we’ve added support for it in iOS 26.4 beta. This is sufficiently ‘bleeding edge’ that the docs haven’t hit the Developer website yet. But the APIs are in the iOS 26.4 beta SDK (I’m using Xcode 26.4b3, build 17E5179g) and there’s documentation in Xcode itself. To set up a listener: let devices: WAPublisherListener.Devices = … specific devices … let listener = try NetworkListener(for: .wifiAware(.addingConnections(from: devices)), using: .parameters({ TCP() }).localPort(12345)) On the client side, do this: let connection: NetworkConnection = … original connection … guard let wifiAwareEndpoint = connection.currentPath?.remoteEndpoint?.wifiAware(port: 12345) else { // … handle the failure … } // … connect to that endpoint … If you
2w
Reply to Bug: Wi-Fi Aware (NAN) Subscriber Mode: nwPath.availableInterfaces Does Not Include nan0 Interface After Successful Peer Connection
[quote='880225022, wu_aaron, /thread/818708?answerId=880225022#880225022, /profile/wu_aaron'] we need to establish multiple additional NWConnection instances … over the Wi‑Fi Aware network [/quote] I don’t think you can do this on currently shipping systems. However, we’ve added support for it in iOS 26.4 beta. This is sufficiently ‘bleeding edge’ that the docs haven’t hit the Developer website yet. But the APIs are in the iOS 26.4 beta SDK (I’m using Xcode 26.4b3, build 17E5179g) and there’s documentation in Xcode itself. To set up a listener: let devices: WAPublisherListener.Devices = … specific devices … let listener = try NetworkListener(for: .wifiAware(.addingConnections(from: devices)), using: .parameters({ TCP() }).localPort(12345)) On the client side, do this: let connection: NetworkConnection = … original connection … guard let wifiAwareEndpoint = connection.currentPath?.remoteEndpoint?.wifiAware(port: 12345) else { // … handle the failure … } // … connect to that endpoint … If you
2w
Reply to Biometrics prompt + private key access race condition on since iOS 26.1
[quote='880086022, smjkrk, /thread/814261?answerId=880086022#880086022, /profile/smjkrk'] we still get this issue with iOS 26.3 and 26.3.1. [/quote] Bummer. At this point I think I’m gonna double down on my earlier suggestion to file a bug about this. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: Privacy & Security SubTopic: General Tags:
2w
EASession(accessory:forProtocol:) always returns nil — MFI accessory iAP2
EASession(accessory:forProtocol:) always returns nil — MFI accessory iAP2 Platform: iOS 17+ | Hardware: Custom MFI-certified accessory (USB-C, iAP2) | Language: Swift Problem We have a custom MFI-certified accessory communicating over USB-C using ExternalAccessory. The app calls EASession(accessory:forProtocol:) after receiving EAAccessoryDidConnect but it always returns nil. We never get past session creation. What we have verified We captured a sysdiagnose on-device and analysed the accessoryd-packets log. The full iAP2 handshake completes successfully at the OS level: USB attach succeeds MFI auth certificate is present and Apple-issued Auth challenge and response complete successfully IdentificationInformation is accepted by iOS — protocol string and Team ID are correct EAAccessoryDidConnect fires as expected iOS sends StartExternalAccessoryProtocolSession — the OS-level session is established So the hardware, MFI auth, protocol string, and Team ID are all correct. Despite this,
5
0
150
2w
Filing a Wi-Fi Bug Report
Every now and again I end up helping a developer with a Wi-Fi issue. These fall into two groups: User-level Wi-Fi issues Development Wi-Fi issues A user-level Wi-Fi issue is one where the developer hasn’t created any of the products involved. An example of this is when you’re developing an app for an accessory and iOS is having problems connecting to that accessory but you don’t control the accessory’s firmware. In general, I recommend that you escalate such issues to the accessory vendor. They can then run their own investigation and, if necessary, file their own bug report. A development Wi-Fi issue is one that directly affects one of your products. For example, you’re developing a Wi-Fi accessory and iOS is having problems connecting to it. In that case, the onus is on you [1] to investigate why things are failing. If your conclusion is that iOS is behaving incorrectly, file a bug about that. IMPORTANT If you do file a bug in the context of some forums thread, please post your bu
0
0
36
2w
iOS AirPrint sends print-quality=high when file-type is photo even if user selects “normal”
Hi everyone, I observed a behavior with AirPrint from an iPhone and wanted to confirm if this is expected behavior from iOS. Scenario tested: File type: Photo Print-quality selected by the user: Normal Observation (from packet capture): When checking the PCAP for the request sent from the iPhone, the print-quality attribute is always sent as high, even though the user selected Normal in the UI. Question: Is this an expected behavior in iOS/AirPrint where photos are always sent with print-quality=high regardless of the user-selected print quality? Or could this be a bug?
0
0
58
2w
CloudKit: Efficient way to get user's rank in leaderboard without fetching all records?
CloudKit: Efficient way to get user's rank in leaderboard without fetching all records? I'm building a leaderboard feature using CloudKit's public database and need advice on the best approach to calculate a user's rank efficiently. Current Setup Record Structure: Record Type: LeaderboardScore Fields: period (String): daily, weekly, monthly, allTime score (Int): User's score profile (Reference): Link to user's profile achievedAt (Date): Timestamp Leaderboard Display: Initially fetch first 15 users (sorted by score descending) Paginate to load more as user scrolls Show total player count Show current user's rank (even if not in top 15) The Challenge I can fetch the first 15 users easily with a sorted query, but I need to display the current user's rank regardless of their position. For example: User could be ranked #1 (in top 15) ✅ Easy User could be ranked #247 (not in top 15) ❌ How to get this efficiently? My Current Approach Query records with scores higher than the user's score and count them: // Count how
Replies
3
Boosts
0
Views
146
Activity
2w
Reply to Direction data not available with U2 chip (iPhone 15 Pro and iPhone 16 Pro) when using Murata SR040/SR150 accessory
Having a similar problem, although I'm not sure if it's related to iOS26 or phones with the U2 chip. I am doing peer to peer rather then peer to object, but figured I'd share my findings. iPhone 16 Pro (U2 chip), iOS 26.3.1: NISession created — capabilities: token: true supportsDirection: false supportsCameraAssistance: true supportsExtendedDistanceMeasurement: true supportsPreciseDistanceMeasurement: true iPhone 12 (U1 chip), iOS 18.6.2: NISession created — capabilities: token: true supportsDirection: true supportsCameraAssistance: true supportsExtendedDistanceMeasurement: false supportsPreciseDistanceMeasurement: true What I've found so far: 16 Pro / U2 / iOS 26 (?) 3D direction vector is never available Camera seems to be required for directional convergence Everything seems to be determined by hAngle Seems to start an NI session with dirSrc as 'none' and then resolves to 'hAngle' after camera convergence is complete 12 / U1 / iOS 18 Seems to start an NI session with 'hA
Replies
Boosts
Views
Activity
2w
Reply to Nearby Interaction property supportsDirectionMeasurement returns false and NINearbyObject direction property is nil
Having the same problem, although I'm not sure if it's related to iOS26 or phones with the U2 chip. Worth noting that I am doing peer to peer rather then peer to object, but figured I'd share my findings. iPhone 16 Pro (U2 chip), iOS 26.3.1: NISession created — capabilities: token: true supportsDirection: false supportsCameraAssistance: true supportsExtendedDistanceMeasurement: true supportsPreciseDistanceMeasurement: true iPhone 12 (U1 chip), iOS 18.6.2: NISession created — capabilities: token: true supportsDirection: true supportsCameraAssistance: true supportsExtendedDistanceMeasurement: false supportsPreciseDistanceMeasurement: true What I've found so far, at least the case of the 16 Pro / U2 / iOS 26 (?): 3D direction vector is never available Camera seems to be required for directional convergence Everything seems to be determined by hAngle Placing both a 16 Pro and a 12 face down on a table with rear cameras covered: 12 continues to show position with a dirSrc of '3D'; 16 Pro
Topic: App & System Services SubTopic: General Tags:
Replies
Boosts
Views
Activity
2w
Reply to Recurring FigXPCUtilities / FigCaptureSourceRemote err=-17281 logs when using AVCaptureVideoDataOutput on iOS 26.x
Thanks for this interesting post! I'm not an expert on that field nor that API. Hope one of the engineers on that team can jump into this thread for better info. These specific FigXPCUtilities and FigCaptureSourceRemote logs are almost certainly benign internal framework noise rather than a regression or a flaw in your capture pipeline. Looking up the err=-17281 is a CoreMedia error code that, without knowing here, typically points to a minor XPC synchronization hiccup, a port invalidation, or an asynchronous state mismatch during the setup or teardown of the capture session? I believe this logs are for information only and should be removed. Code paths that silently recovered in older iOS versions often have their log levels elevated in newer releases (or beta releases), resulting in console spam. If your AVCaptureVideoDataOutputSampleBufferDelegate is successfully receiving CMSampleBuffer frames and your preview layer is rendering smoothly. You can safely ignore these logs. If you want to temporari
Replies
Boosts
Views
Activity
2w
not seeing In-App Purchase and Subscriptions
after doing all the steps as in The app version submission must be in the “Prepare for Submission” state There must be at least one IAP/subscription in the “Ready to Submit” state All banking & agreements must set up and in place I am still not seeing the In-App purchase and subscription in my iOS App Version page to add to my newest version slash build
Replies
1
Boosts
0
Views
62
Activity
2w
Reply to Recurring FigXPCUtilities / FigCaptureSourceRemote err=-17281 logs when using AVCaptureVideoDataOutput on iOS 26.x
Similar issue here when starting an ARSession. iOS 26.3.1 on an iPhone 16 Pro. No issues running the same app on an iPhone 12 on iOS 18.6.2 `(Fig) signalled err=-12710 at <>:601 <<<< FigXPCUtilities >>>> signalled err=-17281 at <>:308 <<<< FigCaptureSourceRemote >>>> Fig assert: err == 0 at bail (FigCaptureSourceRemote.m:569) - (err=-17281)`
Replies
Boosts
Views
Activity
2w
Developer account terminated for “feature switching” – need advice on reinstatement
Hey everyone, I’m looking for advice from anyone who’s been through something similar. My Apple Developer account was recently terminated due to what Apple described as “concept or feature switching.” After digging into it more, I believe this happened because I made updates to my app after it was approved without submitting a new version for review. Here’s what I changed: Added a new screen (friends list) that required navigation changes Updated parts of the UI (visual improvements) Added a feature (button that helps users structure a plan) Enabled Google sign-in I did not change payments, subscriptions, or the core purpose of the app. At the time, I didn’t fully understand that these kinds of changes (especially anything affecting navigation or features) need to go through a new App Store submission rather than being updated remotely. I now understand how Apple could see this as bypassing the review process. Since then, I’ve: Stopped all over-the-air/runtime updates Made sure the app matches the la
Replies
0
Boosts
0
Views
42
Activity
2w
Intermittent connectivity issues on iOS 26.4 Beta - Potential iCloud Private Relay conflict
I am investigating a connectivity issue reported by a user running latest iOS 26.4 Public Beta on an iPhone 17 Pro Max. Unfortunately, I am unable to reproduce this behavior on my end as I do not have access to an iPhone 17 Pro Max for testing, and my current devices do not exhibit the issue. However, the user's logs suggest a system-level networking issue : Symptoms: Flutter App (package dio): Requests fail with The connection errored: Failed host lookup: 'mydomain.com' Firebase SDK: Unable to fetch Firestore documents Duration: The outage is random, lasting between 5 to 15 minutes before self-resolving Scope: It affects both Wi-Fi and Cellular data By the way I found this report from another developer experiencing the exact same behavior: I run a mobile app that has millions of users. As of 1-2 weeks ago, we started getting reports that the app isn't working (failing to connect). It then goes back to connecting anywhere between 5 to 15-20 mins later. Every single one of those users was running iOS
Replies
1
Boosts
0
Views
173
Activity
2w
Reply to Can I download the iOS 26 simulator runtime via a download link
Hi! You can download simulator runtimes following this documentation. For example xcodebuild -downloadPlatform iOS -exportPath ~/Downloads will download the iOS simulator runtime in your Downloads folder. On the other machine, you can use xcodebuild -importPlatform path/to/runtime.dmg to install the simulator runtime you just downloaded.
Replies
Boosts
Views
Activity
2w
Reply to Bug: Wi-Fi Aware (NAN) Subscriber Mode: nwPath.availableInterfaces Does Not Include nan0 Interface After Successful Peer Connection
[quote='880225022, wu_aaron, /thread/818708?answerId=880225022#880225022, /profile/wu_aaron'] we need to establish multiple additional NWConnection instances … over the Wi‑Fi Aware network [/quote] I don’t think you can do this on currently shipping systems. However, we’ve added support for it in iOS 26.4 beta. This is sufficiently ‘bleeding edge’ that the docs haven’t hit the Developer website yet. But the APIs are in the iOS 26.4 beta SDK (I’m using Xcode 26.4b3, build 17E5179g) and there’s documentation in Xcode itself. To set up a listener: let devices: WAPublisherListener.Devices = … specific devices … let listener = try NetworkListener(for: .wifiAware(.addingConnections(from: devices)), using: .parameters({ TCP() }).localPort(12345)) On the client side, do this: let connection: NetworkConnection = … original connection … guard let wifiAwareEndpoint = connection.currentPath?.remoteEndpoint?.wifiAware(port: 12345) else { // … handle the failure … } // … connect to that endpoint … If you
Replies
Boosts
Views
Activity
2w
Reply to Bug: Wi-Fi Aware (NAN) Subscriber Mode: nwPath.availableInterfaces Does Not Include nan0 Interface After Successful Peer Connection
[quote='880225022, wu_aaron, /thread/818708?answerId=880225022#880225022, /profile/wu_aaron'] we need to establish multiple additional NWConnection instances … over the Wi‑Fi Aware network [/quote] I don’t think you can do this on currently shipping systems. However, we’ve added support for it in iOS 26.4 beta. This is sufficiently ‘bleeding edge’ that the docs haven’t hit the Developer website yet. But the APIs are in the iOS 26.4 beta SDK (I’m using Xcode 26.4b3, build 17E5179g) and there’s documentation in Xcode itself. To set up a listener: let devices: WAPublisherListener.Devices = … specific devices … let listener = try NetworkListener(for: .wifiAware(.addingConnections(from: devices)), using: .parameters({ TCP() }).localPort(12345)) On the client side, do this: let connection: NetworkConnection = … original connection … guard let wifiAwareEndpoint = connection.currentPath?.remoteEndpoint?.wifiAware(port: 12345) else { // … handle the failure … } // … connect to that endpoint … If you
Replies
Boosts
Views
Activity
2w
Reply to Biometrics prompt + private key access race condition on since iOS 26.1
[quote='880086022, smjkrk, /thread/814261?answerId=880086022#880086022, /profile/smjkrk'] we still get this issue with iOS 26.3 and 26.3.1. [/quote] Bummer. At this point I think I’m gonna double down on my earlier suggestion to file a bug about this. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: Privacy & Security SubTopic: General Tags:
Replies
Boosts
Views
Activity
2w
EASession(accessory:forProtocol:) always returns nil — MFI accessory iAP2
EASession(accessory:forProtocol:) always returns nil — MFI accessory iAP2 Platform: iOS 17+ | Hardware: Custom MFI-certified accessory (USB-C, iAP2) | Language: Swift Problem We have a custom MFI-certified accessory communicating over USB-C using ExternalAccessory. The app calls EASession(accessory:forProtocol:) after receiving EAAccessoryDidConnect but it always returns nil. We never get past session creation. What we have verified We captured a sysdiagnose on-device and analysed the accessoryd-packets log. The full iAP2 handshake completes successfully at the OS level: USB attach succeeds MFI auth certificate is present and Apple-issued Auth challenge and response complete successfully IdentificationInformation is accepted by iOS — protocol string and Team ID are correct EAAccessoryDidConnect fires as expected iOS sends StartExternalAccessoryProtocolSession — the OS-level session is established So the hardware, MFI auth, protocol string, and Team ID are all correct. Despite this,
Replies
5
Boosts
0
Views
150
Activity
2w
Filing a Wi-Fi Bug Report
Every now and again I end up helping a developer with a Wi-Fi issue. These fall into two groups: User-level Wi-Fi issues Development Wi-Fi issues A user-level Wi-Fi issue is one where the developer hasn’t created any of the products involved. An example of this is when you’re developing an app for an accessory and iOS is having problems connecting to that accessory but you don’t control the accessory’s firmware. In general, I recommend that you escalate such issues to the accessory vendor. They can then run their own investigation and, if necessary, file their own bug report. A development Wi-Fi issue is one that directly affects one of your products. For example, you’re developing a Wi-Fi accessory and iOS is having problems connecting to it. In that case, the onus is on you [1] to investigate why things are failing. If your conclusion is that iOS is behaving incorrectly, file a bug about that. IMPORTANT If you do file a bug in the context of some forums thread, please post your bu
Replies
0
Boosts
0
Views
36
Activity
2w
iOS AirPrint sends print-quality=high when file-type is photo even if user selects “normal”
Hi everyone, I observed a behavior with AirPrint from an iPhone and wanted to confirm if this is expected behavior from iOS. Scenario tested: File type: Photo Print-quality selected by the user: Normal Observation (from packet capture): When checking the PCAP for the request sent from the iPhone, the print-quality attribute is always sent as high, even though the user selected Normal in the UI. Question: Is this an expected behavior in iOS/AirPrint where photos are always sent with print-quality=high regardless of the user-selected print quality? Or could this be a bug?
Replies
0
Boosts
0
Views
58
Activity
2w