Overview

We develop an iOS SDK that allows developers to add VoIP capability to their iOS applications. For post-call quality analysis and debugging purposes we do collect SDK API usage and call quality data and send them back through internal HTTP API endpoint, therefore we need to disclose the domain in the privacy manifest. However we do not collect any Personally Identifiable Information and definitely have no intent to use these data for tracking the users like the examples described in https://developer.apple.com/app-store/user-privacy-and-data-use/. Our question is, do we need to set the “NSPrivacyTracking” key to “true” in the privacy, or our SDK actually is not tracking from the Privacy Manifest’s perspective and simply disclosing the data collection type/purpose as well as the domain is sufficient?

I have a simple example to demonstrate... struct MyView: View { var body: some View { Text("WOW") } } struct MyOtherView: View { var body: some View { NavigationStack { Text("WOW") } } } On VisionOS, MyOtherView has a glass background effect that cannot be disabled. glassBackgroundEffect(displayMode: .never) .background(.clear), .foregroundColor(.clear), none of them work. I then resorted to the SwiftUIIntrospect package to try set .clear on various child objects of the NavigationStack but nothing is working. I am in control of my own glass containers. I have a couple with space between them, but with the NavigationStack it sets a background behind both of them ruining the effect. This is what MyOtherView renders as: I'm looking for it to be completely transparent except the text. For now I will have to roll my own navigation.

In my SwiftUI view, I try to load the image from data. var body: some View { Group{ if let data = model.detailImageData, let uiimage = UIImage(data: data) {// no memory issue Image(uiImage: uiimage) .resizable() .scaledToFit() } } } But I want to get the HDR style of my image, so I use if let data = model.detailImageData, let uiimage = UIImageReader.default.image(data:data){ //memory leaks!!! When I change the data, the memory of the previous image is never freeed. finally caused my app to crash. You can see it from the Instrument screenshot.

Trabalho numa empresa que presta serviço implementando, mantendo e publicando sistemas para prefeituras. Fizemos agora um app para uma prefeitura mas na hora de publicar, a Apple está rejeitando pois diz que não podemos publicar em nome de outra empresa. No primeiro envio, rejeitaram com: Guideline 4.1 - Design - Copycats The app or its metadata appears to contain potentially misleading content. Specifically, the app includes content that resembles Sistema da Prefeitura without the necessary authorization. Next Steps Please demonstrate your relationship with any third-party brand owners represented in the app. Pegamos com a prefeitura um documento assinado digitalmente informando que somos os responsáveis pelos sistemas deles, autorizando tudo etc... Fizemos um novo envio para revisão. Porém, agora foi rejeitado com: Guideline 5.1.1 - Legal - Privacy - Data Collection and Storage The app must be published under a seller and company name that is associated with the organization or company providing the services. In this case, the app must be published under a seller name and company name that reflects the MUNICÍPIO DE *** name. The guideline 5.1.1(ix) requirements give users confidence that apps operating in highly regulated fields or that require sensitive user information are qualified to provide these services and will responsibly manage their data. Next Steps To resolve this issue, it would be appropriate to take the following steps: The app must be published under a seller name and company name that reflects the MUNICÍPIO DE *** name. If you have developed this app on behalf of a client, you may resubmit the app through their account, if they have one. You may also request an update to the company name on your account by having the Account Holder edit the account information. Please note that you cannot resolve this issue with documentation showing permission to publish this app on behalf of the content owner or institution. Ou seja, agora estão rejeitando se contradizendo no que pediram previamente. A prefeitura não possui conta de desenvolvedor na Apple. Não tem como eles publicarem isso. Alguém já passou por isso? Tem ideia do que podemos fazer? Desde já agradeço.

X button not working in the wish list page of itunes #713black

I use this code to show the Image in HDR in SwiftUI struct HDRImageView: UIViewRepresentable { // Set up a common reader for all UIImage read requests. static let reader: UIImageReader = { var config = UIImageReader.Configuration() config.prefersHighDynamicRange = true return UIImageReader(configuration: config) }() let data:Data? let enableHDR:Bool func makeUIView(context: Context) -> UIImageView { let view = UIImageView() view.preferredImageDynamicRange = enableHDR ? .high : .standard update(view) // Set this view to fit itself to the parent view. view.setContentCompressionResistancePriority(.defaultLow, for: .horizontal) view.setContentCompressionResistancePriority(.defaultLow, for: .vertical) view.setContentHuggingPriority(.required, for: .horizontal) view.setContentHuggingPriority(.required, for: .vertical) return view } func updateUIView(_ view: UIImageView, context: Context) { update(view) } func update(_ view: UIImageView) { autoreleasepool{//not working if let data = data { view.image = nil//set to nil first is not working view.image = HDRImageView.reader.image(data: data) } else { view.image = nil } view.preferredImageDynamicRange = enableHDR ? .high : .standard } } } But when I update the input data, seems that the old image data can not be freeed. After several changes, the app takes too much memory and crash. I found it's the VM:ImageIO_Surface_Data and the VM_Image_IO take up the memory. If I change the HDRImageView into a normal Image(uiimage:UIImage(data:)) It no longer have this issue. Is it a memory leak? and how to solve this. Update: I then tried using Image(_:cgImage), and it appear to be the same result.

Hey everyone, I'm currently working on an app where I've already implemented a packet tunnel provider. Now, I'm looking to introduce a content filter. One crucial feature I need is the ability to read the bundle ID of the app originating the network flows. However, I've hit a roadblock when combining both components; When I run the content filter sans packet tunnel provider, I can read the originating app's bundle ID for network flows just fine. But when I add packet tunnel provider, the app's bundle ID defaults to my own app's bundle ID, which is unexpected. Has anyone else encountered this? Any thoughts on why it's happening or how to fix it? Cheers!

I have a driving tracking app I'm working on that properly starts tracking and logging location when the app is in the foreground or background. I use a buffer/queue to keep recent locations so when a trip ramps up to driving speed I can record that to work back to the start location just before the trip starts. This works great, however, in background mode when the user does not have the app open it will record locations but not until a significant location change is detected. The buffering I do is lost and the location only starts tracking several hundred yards or more after the trip has started. Does anyone have any suggestions or strategies to handle this chicken and the egg scenario?

Hello, I have a problem in the Xcode 15.0 where the custom Dynamic library cannot be found during build. The dynamic library is built for iOS 16 and I have added it to "Link Binary with Libraries" and also to "Embed Libraries" as Destination: Framework. In the General->Frameworks, Libraries and Embedded Content I can see the library is loaded and "Embhed&Sign" option is set. In Build Settings the "Library search path" is also set to the location of library "$(PROJECT_DIR)/test/lib" Library is available in this location: $(PROJECT_DIR)/test/lib I can build the project without any issues. But when I try to run the application, I get below error: dyld[1076]: Library not loaded: libtest-xx.dylib Referenced from: <4A9...> Reason: tried: '/usr/lib/system/introspection/libtest-xx.dylib' (no such file, not in dyld cache //libtest-xx.dylib' (no such file) Can anyone please let me know what is the issue here and how to correctly bundle dynamic library with the application? Thanks in advance

I am new to coding so pardon my naivety. I made a simple app for my company where customers can place orders and leave their names and phones numbers. Upon placing an order the app creates a collection in Google Firebase then generates an email with some HTML code. My app does not use any API's directly, and I believe I received the warning email solely because of the Firebase SDK like many others. I updated my app with what I believe to be proper "declaration of the data collected by my app or by third-party SDKs" according to https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_data_use_in_privacy_manifests - but I am wondering if I actually did it correctly! See Attached

Hi! I watched WWDC 2019 Optimizing App Launch video and can't see the Lifecycle phases when I Profile my App. I'm using Xcode 15.2 with Instruments 15.2, and SwiftUI as UI framework. Here is a screenshot of what I get. It's there another tool or another way to get this information? Thanks! Alfonso.

✖ Something went wrong when submitting your app to Apple App Store Connect. But here is the error that is returned to me in my console, so I can do it with the command lines by EAS

hi I have been using WKWebView embedded in a UIViewRepresentable for displaying inside a SwiftUI View hierarchy, but when I try the same code on 17,5 beta (simulator) the code fails. In fact, the code runs (no exceptions raised or anything) but the web view does not render. In the console logs I see: Warning: -[BETextInput attributedMarkedText] is unimplemented Error launching process, description 'The operation couldn’t be completed. (OSStatus error -10814.)', reason '' The code I am using to present the view is: struct MyWebView: UIViewRepresentable { let content: String func makeUIView(context: Context) -> WKWebView { // Javascript that disables pinch-to-zoom by inserting the HTML viewport meta tag into <head> let source: String = """ var meta = document.createElement('meta'); meta.name = 'viewport'; meta.content = 'width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no'; var style = document.createElement('style'); style.type = 'text/css'; style.innerHTML = '*:focus{outline:none}body{margin:0;padding:0}'; var head = document.getElementsByTagName('head')[0]; head.appendChild(meta); head.appendChild(style); """ let script: WKUserScript = WKUserScript(source: source, injectionTime: .atDocumentEnd, forMainFrameOnly: true) let userContentController: WKUserContentController = WKUserContentController() let conf = WKWebViewConfiguration() conf.userContentController = userContentController userContentController.addUserScript(script) let webView = WKWebView(frame: CGRect.zero /*CGRect(x: 0, y: 0, width: 1000, height: 1000)*/, configuration: conf) webView.isOpaque = false webView.backgroundColor = UIColor.clear webView.scrollView.backgroundColor = UIColor.clear webView.scrollView.isScrollEnabled = false webView.scrollView.isMultipleTouchEnabled = false if #available(iOS 16.4, *) { webView.isInspectable = true } return webView } func updateUIView(_ webView: WKWebView, context: Context) { webView.loadHTMLString(content, baseURL: nil) } } This has been working for ages and ages (back to at least ios 15) - something changed. Maybe it is just a problem with the beta 17.5 release?

Address validation failed. Please update legal entity address 2)A new version of your Paid Applications agreement is available. 3)To sell your app or other in-app purchases, you must sign the Paid Applications Agreement. 4)To receive payments from Apple, you must add a bank account. 5)To meet the requirements of the Paid Applications agreement and receive payments, you must add a U.S. tax form.

New versions of AppKit/Mac Catalyst apps that use Google's Sign In framework are being rejected by App Store Review for the past two weeks. Reason shared was: The user is taken to the default web browser to sign in or register for an account, which provides a poor user experience. And also citing: Data Collection & Storage guidelines -> https://developer.apple.com/app-store/review/guidelines/#data-collection-and-storage Opening macOS' default web browser has been a native behavior of Mac apps when using SFSafariViewController with ASWebAuthenticationSession, which is required, since iOS 13, for securely/privately logging in users. As far as I could investigate, there hasn't been any updates to the guidelines that would indicate any required changes to developers in regards to how login works for macOS apps. Are there any steps developers need to take to get updates approved while still providing users with Google's Sign in? As reference, there is an on-going discussion on GoogleSignIn repo about this issue affecting multiple developers and apps: https://github.com/google/GoogleSignIn-iOS/issues/388

Howdy, I have a nasty feeling that the answer to my question is "Y'all cain't do that!", but I figure I'll ask, anyway. THE SAD STORY (GET YOUR HANKY): We have an app that implements Sign [up|in] with Apple. It does it pretty well, with no password visible to the user, and a pretty smooth UX. The issue is what happens when users bork their install. We don't think it will happen often, but want to be able to give the user the best way out, if possible. With the regular (non-SiiA) method, they bonk on a "Forgot Password" button, and the app sends them a new password. We can't do that, with SiiA. The password is stored in the app (in the keychain, so it's very persistent, and shared across devices), and it would a Very Bad Security Hole, to allow users to simply send a new password to the server (the other method generates a rando in the server), which is what would happen, with our method of handling the password. It would also be equally bad, if the server could simply send a new password to the user, directly to their device (the other method sends an email, based on the sign-in information on the server). So the user needs to delete their keychain data completely, which we can easily do, but that does not deal with their SiiA stuff, stored on Apple's server. This is what Apple tells us to do, to delete that. WHICH BEGS THE QUESTION: My question is: Is there a URL scheme that I can use to directly open that panel? If so, it would allow us to create a screen that helps the user to do all the deletions (on the device, our server, and the Apple server).

Hi guys, i want to ask how When i press remove. This app is unable to be removed right now.

Hello, I believe I'm experiecing a bug within the AppStoreConnect dev console. When I try to submit a new version of my game for review I recieve an error message stating The items below are required to start the review process: There are still leaderboard image uploads in progress. One might think that this problem should have an obvious solution: wait for the leaderboard images to load and try again. Unfortunately this is impossible, because all images are already loaded. They are also being successfully displayed in the console interface and even in my game itself. I tried to remove all images, but that didn't help. I've also noticed that leaderboard management interface in the console was updated in the past month or two. I think that might be somehow related to the problem (something from old UI got cached and now isn't affect by new UI). I've also filed a request (102270407515) to the Apple Support, but didn't get any answer (aside from the request is registered). Is there any chance I get an answer from Apple Support here on the forum?

Many of Apple's tutorials on SwiftData are written alongside SwiftUI, including the sample code. Would it be a bad idea to use SwiftData separately? If I don't use SwiftUI, would it be wiser to choose a different database instead?

Hello, I found a user that has two originalTransactionIds for the same subscriptionGroupIdentifier. I thought that: originalTransactionId does not change in case of upgrade/downgrade, cancellation/re-subscribtion user can see only products within single subscription group A, so if there is a subscription group B, user will not use any products from B (so new originalTransactionId will not be created because we're still within same subscription group) I can see for this user that new originalTransactionId was given when transactionReason was PURCHASE and storefrontId, price and currency have changed in comparison to previous RENEWAL transactions. Can new originalTransactionId be given to the user when purchasing subscription from different country than previously? Thanks a lot for clarification, Best regards, Maria