The same store kit configuration file works in iOS and iPadOS, but not in macOS for the same multi platform application project with a single scheme. Here’s a more detailed write up with the sample code and screenshots. When the simple app is run on https://www.reddit.com/r/SwiftUI/s/KJsYcggWOa EDIT: I’m using Xcode 16.4
Search results for
İOS 26 beta battery %1
250,967 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
Here's the code. It works on iOS/iPadOS but not macOS for the same .storekit file??? import SwiftUI import StoreKit public enum License: String, CaseIterable, Identifiable { public var id: String { self.rawValue } case subscriptionLifetimePremium = subscription.lifetime case subscriptionYearlyPremium = subscription.yearly case subscriptionMonthlyPremium = subscription.monthly } struct ContentView: View { var body: some View { VStack { Image(systemName: globe) .imageScale(.large) .foregroundStyle(.tint) Button(StoreKit Test) { Task { @MainActor in // Request our offers from the app store let productIDs = License.allCases.map { $0.rawValue } print(productIDs: (productIDs)) let productsOffered = try await Product.products(for: Set(productIDs)) print(productsOffered: (productsOffered)) } } } .padding() } }```
Topic:
App & System Services
SubTopic:
StoreKit
Tags:
[quote='800331021, packagesdev, /thread/800331, /profile/packagesdev'] Also why is there a tag for InstallerJS and not one for Installation in the Developer Forums? [/quote] Again with the why questions (-: Seriously though, I agree that there should be a tag for Mac installer packages. Although I’d probably call it Mac Installer rather than just Installation, because otherwise it’ll get flooded with iOS stuff. I can’t fix this immediately, but I’ve put it on my to-do list so that it doesn’t slip through the cracks. [quote='800331021, packagesdev, /thread/800331, /profile/packagesdev'] Has this element always worked correctly in the past? [/quote] Clearly no, in that you’re seeing it fail on 10.14. As to what you should do about this, it depends on whether you actually need to support 10.14 or earlier systems? [quote='800331021, packagesdev, /thread/800331, /profile/packagesdev'] Generally speaking, this documentation is missing examples for a lot of the elements. [/quote] It’s also in the D
Topic:
Developer Tools & Services
SubTopic:
General
Tags:
This is is going to be tricky. An app’s icon is part of its bundle, and thus modify the icon will break the seal on the code signature. You don’t want to leave the user with an app with a broken code signature because sooner or later Gatekeeper look at the app, notice the broken signature, and kvetch. Now, what you could do is something like: Build, sign, and notarise all the variants of your app. From those variants, construct an installer that only contain one primary variant of your app and the diffs for all the other variants. Have that installer install the primary and then apply the relevants diffs. The end result is an app that’s correctly signed and notarised, and thus unlikely to hit notary problems. However, doing this is quite a bit of work. The key problems is that critical parts of the code signature are stored within the app’s main executable Mach-O image. If you store the diffs as a list of files, you’ll need N copies of the main executable, which presumably is quite large. There are w
Topic:
App & System Services
SubTopic:
General
Tags:
Hi, I am experiencing an issue where Xcode displays a Provisioning profile doesn't support the capability error for the User Assigned Device Name capability, despite it being approved by Apple and visible in our provisioning profile on the Developer Portal. Background We have completed and submitted the required capability request form to Apple for the User Assigned Device Name capability and received approval. The capability appears correctly in our provisioning profile on the Apple Developer Portal and shows among the enabled capabilities alongside other standard capabilities like In-App Purchase and Push Notifications. Issue However, Xcode consistently displays the error message when trying to enable the User Assigned Device Name capability in our project settings, preventing successful builds with this functionality. Troubleshooting Steps Attempted We have tried multiple troubleshooting steps including: Regenerating provisioning profiles Performing clean builds Clearing DerivedData Manually installing pro
Topic:
Code Signing
SubTopic:
Certificates, Identifiers & Profiles
Tags:
Xcode
Provisioning Profiles
Reply to
Xcode not recognizing approved User Assigned Device Name capability in provisioning profile
The majority of issues like this are caused by limitations imposed on the managed capability. For example: You might have been granted it for development only. You might have been granted it for a specific App ID. See Finding a Capability’s Distribution Restrictions for info on how to investigate the first point. ps If this is Team ID 2________2, my view of our records shows that: The capability is limited to single App ID, 2________2.n__.r____.a__. And to Development and Ad Hoc distribution, not for the App Store distribution you’d need to actually ship your app on the store. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic:
Code Signing
SubTopic:
Certificates, Identifiers & Profiles
Tags:
Facing the same exact issue. We have a bottom navigation bar that is fixed with bottom: 0. After closing the keyboard on an input, the navigation bar is no longer at the very bottom while scrolling down. I submitted feedback FB20249802. find a working example here: https://stackoverflow.com/questions/79758083/ios-26-safari-visualviewport-change-after-dismissing-keyboard
Topic:
Safari & Web
SubTopic:
General
Tags:
Trying to upload an iOS26 app archive with Xcode 26 beta 7 and getting ITMS-90717: Invalid large app icon, meaning my app is not eligible for TestFlight testing. My App contains an IconComposer .icon asset, so I'm not sure what it's complaining about. I'm not seeing anything in the release notes about this, and I'm not sure if I'm doing something wrong or not.
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
App Store Connect
Organizer Window
Right now, the traffic light buttons overlapped on my iPad app top corner on windows mode (full screen is fine). How do I properly design my app to avoid the traffic light buttons? Detect that it is iPadOS 26?
Topic:
UI Frameworks
SubTopic:
SwiftUI
First the Model: import Foundation import SwiftData //Model for Earned Value Analysis @Model final class CostReport{ var aCWP: Double //Actual Cost of Work Performed var bCWP: Double //Budgeted Cost of Work Performed var bCWS: Double // Budgeted Cost of Work Scheduled var cumACWP: Double// Cumlative Actual Cost of Work Performed var cumBCWP: Double // Cumlative Budgeted Cost of Work Performed var cumBCWS: Double // Cumlative Budgeted Cost of Work Scheduled var startDateOfPeriod: Date var endDateOfPeriod: Date var contract: Contract? init(aCWP: Double = 0.0, bCWP: Double = 0.0, bCWS: Double = 0.0, cumACWP: Double = 0.0, cumBCWP: Double = 0.0, cumBCWS: Double = 0.0, startDateOfPeriod: Date = .now, endDateOfPeriod: Date = .now, contract: Contract) { self.aCWP = aCWP self.bCWP = bCWP self.bCWS = bCWS self.cumACWP = cumACWP self.cumBCWP = cumBCWP self.cumBCWS = cumBCWS self.startDateOfPeriod = startDateOfPeriod self.endDateOfPeriod = endDateOfPeriod self.contract = contract } } @Model //Model for Contracts final c
Topic:
Developer Tools & Services
SubTopic:
Xcode
Found the issue: In a one to many relationship to be able to enter the one side of the relationship you need to identify the many side, even if you are not entering any values for the many side. In this case the many side is Contracts and a state variable needs to be declared @State private var contracts: [Contract] = [] with an empty array.
Topic:
Developer Tools & Services
SubTopic:
Xcode
Hi, When submitting my iOS app that integrates the TwilioVoice SDK (v6.12.1+), validation fails with the following error: Upload failed with errors: Validation failed The app references non-public selectors in Payload/careqb.app/careqb: _isKeyDown, _modifiedInput, _modifierFlags (ID: 34774fb-ba69-4131-904f-694aead106d7) Steps to reproduce: Integrate TwilioVoice using CocoaPods (v6.12.1). Archive the app in Xcode 16.x. Validate for App Store Connect. Question: Is this a known false positive in App Store validation, or is TwilioVoice exposing private APIs internally? What’s the recommended way to proceed until Twilio releases a fix? Thanks, Ashutosh
Im facing the same since 26 ios beta versions. The same behavior like hibye was mentioned here. It wasnt happened on ios18. i have opened a feedback FB19889436 few weeks ago, however the current explenation in this topic describe better the issue.
Topic:
Safari & Web
SubTopic:
General
Tags:
Yes, I also understand the notification confirmation method that way. However, I’m curious to know if there’s a publicly available API that allows notifications to be expanded with a single tap (not a long-press), similar to the new battery-related notifications introduced in iOS 26.
Topic:
App & System Services
SubTopic:
Notifications
Tags:
In iOS 26, I can check the notification that arrives to the user when the AirPods or Apple Watch is fully charged. When tap the notification, notification only expands and does not include actions such as moving to an app. I checked the documents of UserNotification and UNNotificationServiceExtension, but I couldn't find what I wanted. I can expand by long-tapping as default, but I'm looking for a way to expand it without entering the app when I tap the notification. I wonder if there is an API that I missed or if it's not publicly supported. thank you for your support.