Search results for

“translate scheme”

6,658 results found

Post

Replies

Boosts

Views

Activity

Reply to App Store Connect
On the App Distribution tab, when I submit for approval, I get an error requiring me to choose a build. When I select Add Build, I get the window with all my uploaded builds but I cannot select them, the radio buttons are disabled. Good point, I have added translations (nothing suggested they were mandatory) and that has reduced the error list of things preventing me from submitting for approval. I think I may need my subscription to be approved before I add in a trial period, so need to solve point 1 above first. On app versions, is there an enforced sequence? I am trying to test Version 3.0 of my app in Test Flight, I uploaded a bundle from Xcode with Version 3.0 but thought that might be the issue so expired it and created a 1.0 bundle. So the build options to select are 1.0 that I want to test, but 3.0 is also in the list.
Apr ’25
Reply to Code Coverage not showing properly?
Yeah the tests call into the application code and all the tests pass. And I verified the settings have code coverage on. The issue is that the project is so old, I feel like something is conflicting in the settings? I was very confused by the different settings that seem to affect code coverage (the scheme settings both when using test plans and when not, CLANG_ENABLE_CODE_COVERAGE, GCC_GENERATE_TEST_COVERAGE_FILES etc) But I hear you, it might just too complex to debug in the abstract. I was hoping there would be an easy solution, cause the tests do run, and I am seeing 'number go up' as I add tests. I just don't have access to file-based coverage. It seems to be just overall coverage stats (based on the image in the post).
Apr ’25
Reply to How to implement the "Set Up Codes In" feature
Hi! Apps that support the otpauth:// URL scheme are displayed in that section and available to be set as the default handler. You may also be interested in a related API for providing one time codes for AutoFill: https://developer.apple.com/documentation/authenticationservices/providing-one-time-passcodes-to-autofill?language=objc
Topic: Privacy & Security SubTopic: General Tags:
Apr ’25
Reply to Storing metadata alongside files outside of sandbox
[quote='834124022, solemnwarning, /thread/780237?answerId=834124022#834124022, /profile/solemnwarning'] I have not been able to get it to work in any other cases [/quote] Yeah. That’s pretty much what I expected )-: Unfortunately that rules out the option of storing your metadata as a related file. The remaining options I see are: Store it in extended attributes. Store it in a database in your sandbox. Both of these have clear drawbacks. Regarding the first, you wrote: [quote='780237021, solemnwarning, /thread/780237, /profile/solemnwarning'] I've considered adding support for storing the metadata as an extended attribute instead (which breaks compatibility, and won't translate when the file is on a FAT/etc filesystem or network share), [/quote] On volumes without extended attribute support the system will store extended attributes in an AppleDouble file. That’s a public file format, so you could support it on other platforms. Regarding the second approach, you wrote: [quote='834280022, solemnwarning
Topic: App & System Services SubTopic: Core OS Tags:
Apr ’25
The identity used to sign the executable is no longer valid
Hi there, When I deploy my app to the iPhone for testing, I get the following error: Failed to verify code signature of /var/installd/Library/Caches/com.apple.mobile.installd.staging/temp.4gpZFc/extracted/c_mll.app : 0xe8008018 (The identity used to sign the Please ensure that the certificates used to sign your app have not expired. If this issue persists, please attach an IPA of your app when sending a report to Apple. executable is no longer valid.) My account was mistakenly deactivated by Apple last month. After appealing, Apple restored it at the end of last month. Currently, my Apple Developer account seems to be working fine. Today, I recreated the developer certificate and identifier, added the account in XCode, everything seemed fine, and I clicked the XCode button (Start the active scheme). The build was successful, but I got the error: Failed to verify code signature of /var/installd/Library/Caches/com.apple.mobile.installd.staging/temp.4gpZFc/extracted/c_mll.app : 0xe8008018 (The identity
7
0
495
Apr ’25
Reply to custom-URL-handling method not being called
Thanks for the reply Albert. I simply said that the app is not finished, so I have not archived it and uploaded it to App Store Connect. It exists, however, and is nearly at a testable state. It builds and runs just fine on devices and simulators, and when I set up a custom URL scheme in the project and typed a conforming URL into Safari's address bar (in a simulator), iOS offered to open the URL in my app as expected. Unfortunately, once the app opened, the documented method for receiving the URL was never called. Based on the information in this thread, it appears that custom URLs may be deprecated or out of favor. So I have now implemented universal links, following all the steps Apple provides in the document you linked to above. This includes placing the necessary JSON file at a domain I control, and I have confirmed that it's accessible. I also set up entitlements in my project, with applinks URLs specified. In the doc you linked to, the method under how to handle a universal link in iOS and tv
Topic: UI Frameworks SubTopic: General Tags:
Apr ’25
Reply to TESTFLIGHT: The requested app is not available or doesn t exist
I have the same problem, evem when i build and submit the app with Expo App Services, my app's new build appears in Testflight, but I can't install it: The app is not available or doesnt exist (I translated it from french). However, some of my friends who have an old build on their iPhone can still open it on TestFlight, despite I deleted the old app and builds... I don't understand what is going on tbh.
Apr ’25
Failed to open URL : Error Domain=NSOSStatusErrorDomain Code=-10814
Regarding the Issue with URL Scheme Not Working。 Hello, our app on the App Store has the following CFBundleURLTypes configuration: We've discovered that the qmkege:// URL scheme is failing to open the app. Steps to Reproduce: 1、We downloaded the installation package from the App Store 2、Entered qmkege:// in Safari, but it fails to launch our app。 The system logs show the following: Key Observation: This issue is not consistently reproducible. In most cases, when we install the app directly from the App Store (without VPN), it works fine. However, the problem occurs when downloading the app through the App Store while connected via VPN. Looking forward to your feedback.
1
0
100
Apr ’25
Storing metadata alongside files outside of sandbox
Hello all, I'm the developer of REHex, a hex editor which I have been distributing as an app bundle outside of the app store for a few years. REHex allows assigning various bits of metadata (comments, data types, etc) which get stored as filename.rehex-meta alongside the original filename, this works fine when the app is just a standalone bundle, however, when distributed via the app store, sandboxing seems to be mandatory, and there doesn't appear to be any obvious way to get permission to read/write such files. As fallbacks, I've considered adding support for storing the metadata as an extended attribute instead (which breaks compatibility, and won't translate when the file is on a FAT/etc filesystem or network share), or popping up the save/load dialog a second time for the user to select a .rehex-meta file, adding it to the list of whitelisted files for the application (keeps compatibility, but UX is clunky). Are there any ways I can work around this, or perhaps other methods I should consider fo
5
0
187
Apr ’25
XcodeKit module not found, but why?
I'm working on a plugin, and that target works just fine. I made another target so I can test some computation functions. It doesn't need much from XcodeKit, just some of the structures. I added XcodeKit and Cocoa, but the import XcodeKit just says no such module. If I switch to the plugin target, it's just fine. I've compared both schemes, but I don't see difference which would affect finding the framework.
2
0
131
Apr ’25
Reply to ASWebAuthenticationSession + https iOS <17.4
If you want a callback URL that starts with https, you must use the .https(...) callback type, which is only available on iOS 17.4 and later. Prior to this, ASWebAuthenticationSession required the use of a custom scheme (i.e. a scheme that's not http/https). For example, your callback URL in that case might look like myapp://auth/callback. Some services may warn against using custom schemes, as they may have security difficulties on some platforms. This is because, unlike https callbacks, any app could claim the myapp:// scheme, potentially resulting in your auth callback going to the wrong app. However, ASWebAuthenticationSession was specifically built to mitigate this concern, ensuring only your app will receive callbacks for that scheme when it's opened via ASWebAuthenticationSession.
Topic: Privacy & Security SubTopic: General Tags:
Apr ’25
Reply to Issues with Opening iOS Settings from App
The specific settings pages you can navigate to are documented here: Supported URL Schemes. Unfortunately it doesn’t currently include Wi-Fi settings. The latest version of the app_settings Flutter library does seem to document this limitation under AppSettingsType.wifi here: https://pub.dev/documentation/app_settings/latest/app_settings/AppSettingsType.html
Apr ’25
Reply to App Store Connect
But for some reason, I cannot select a build - Why not? What is stopping you? What happens when you click the plus button and the popup appears with the various builds listed? You're telling us you cannot select a build for some reason, but you don't tell us what's actually happening, so we can't actually help you. Have you added the translations? I think it requires at least one translation, even if it's just English. I think that's in the App Store Localizations bit. Take a look at the Help pages: https://developer.apple.com/help/app-store-connect/ There is a section on Managing Subscriptions.
Apr ’25
XCode reverts CoreData's .xccurrentversion
I am experiencing an issue where XCode reverts .xccurrentversion file in my iOS app to the first version whenever xcodebuild is run or whenever XCode is started. This means I can build the app and run tests in XCode if I discard the reversion .xccurrentversion on XCode start. However, testing on CI is impossible because the version the tests rely on are reverted whenever xcodebuild is run. The commands I run to reproduce the issue ❯ git status Changes not staged for commit: (use git add ... to update what will be committed) (use git restore ... to discard changes in working directory) modified: Path/.xccurrentversion no changes added to commit (use git add and/or git commit -a) ❯ git checkout Path/.xccurrentversion Updated 1 path from the index ❯ git status nothing to commit, working tree clean ❯ xcodebuild -scheme Scheme -configuration Configuration -sdk iphonesimulator -destination 'platform=iOS Simulator,name=iPhone 16 Pro,OS=latest' -skipPackagePluginValidation -skipMacroValidation
16
0
677
Apr ’25
Reply to App Store Connect
On the App Distribution tab, when I submit for approval, I get an error requiring me to choose a build. When I select Add Build, I get the window with all my uploaded builds but I cannot select them, the radio buttons are disabled. Good point, I have added translations (nothing suggested they were mandatory) and that has reduced the error list of things preventing me from submitting for approval. I think I may need my subscription to be approved before I add in a trial period, so need to solve point 1 above first. On app versions, is there an enforced sequence? I am trying to test Version 3.0 of my app in Test Flight, I uploaded a bundle from Xcode with Version 3.0 but thought that might be the issue so expired it and created a 1.0 bundle. So the build options to select are 1.0 that I want to test, but 3.0 is also in the list.
Replies
Boosts
Views
Activity
Apr ’25
Reply to Code Coverage not showing properly?
Yeah the tests call into the application code and all the tests pass. And I verified the settings have code coverage on. The issue is that the project is so old, I feel like something is conflicting in the settings? I was very confused by the different settings that seem to affect code coverage (the scheme settings both when using test plans and when not, CLANG_ENABLE_CODE_COVERAGE, GCC_GENERATE_TEST_COVERAGE_FILES etc) But I hear you, it might just too complex to debug in the abstract. I was hoping there would be an easy solution, cause the tests do run, and I am seeing 'number go up' as I add tests. I just don't have access to file-based coverage. It seems to be just overall coverage stats (based on the image in the post).
Replies
Boosts
Views
Activity
Apr ’25
Reply to How to implement the "Set Up Codes In" feature
Hi! Apps that support the otpauth:// URL scheme are displayed in that section and available to be set as the default handler. You may also be interested in a related API for providing one time codes for AutoFill: https://developer.apple.com/documentation/authenticationservices/providing-one-time-passcodes-to-autofill?language=objc
Topic: Privacy & Security SubTopic: General Tags:
Replies
Boosts
Views
Activity
Apr ’25
Reply to Storing metadata alongside files outside of sandbox
[quote='834124022, solemnwarning, /thread/780237?answerId=834124022#834124022, /profile/solemnwarning'] I have not been able to get it to work in any other cases [/quote] Yeah. That’s pretty much what I expected )-: Unfortunately that rules out the option of storing your metadata as a related file. The remaining options I see are: Store it in extended attributes. Store it in a database in your sandbox. Both of these have clear drawbacks. Regarding the first, you wrote: [quote='780237021, solemnwarning, /thread/780237, /profile/solemnwarning'] I've considered adding support for storing the metadata as an extended attribute instead (which breaks compatibility, and won't translate when the file is on a FAT/etc filesystem or network share), [/quote] On volumes without extended attribute support the system will store extended attributes in an AppleDouble file. That’s a public file format, so you could support it on other platforms. Regarding the second approach, you wrote: [quote='834280022, solemnwarning
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Apr ’25
Point out a translation problem in the Apple Human Interface Guide (Simplified Chinese)
辅助功能 | Apple Developer Documentation In the illustration on this page related to Prefer system-defined colors, Light is incorrectly translated as 细体. However, in the context of this article, translating it as 浅色 (light color) would be a more appropriate choice.
Replies
1
Boosts
0
Views
84
Activity
Apr ’25
The identity used to sign the executable is no longer valid
Hi there, When I deploy my app to the iPhone for testing, I get the following error: Failed to verify code signature of /var/installd/Library/Caches/com.apple.mobile.installd.staging/temp.4gpZFc/extracted/c_mll.app : 0xe8008018 (The identity used to sign the Please ensure that the certificates used to sign your app have not expired. If this issue persists, please attach an IPA of your app when sending a report to Apple. executable is no longer valid.) My account was mistakenly deactivated by Apple last month. After appealing, Apple restored it at the end of last month. Currently, my Apple Developer account seems to be working fine. Today, I recreated the developer certificate and identifier, added the account in XCode, everything seemed fine, and I clicked the XCode button (Start the active scheme). The build was successful, but I got the error: Failed to verify code signature of /var/installd/Library/Caches/com.apple.mobile.installd.staging/temp.4gpZFc/extracted/c_mll.app : 0xe8008018 (The identity
Replies
7
Boosts
0
Views
495
Activity
Apr ’25
Reply to custom-URL-handling method not being called
Thanks for the reply Albert. I simply said that the app is not finished, so I have not archived it and uploaded it to App Store Connect. It exists, however, and is nearly at a testable state. It builds and runs just fine on devices and simulators, and when I set up a custom URL scheme in the project and typed a conforming URL into Safari's address bar (in a simulator), iOS offered to open the URL in my app as expected. Unfortunately, once the app opened, the documented method for receiving the URL was never called. Based on the information in this thread, it appears that custom URLs may be deprecated or out of favor. So I have now implemented universal links, following all the steps Apple provides in the document you linked to above. This includes placing the necessary JSON file at a domain I control, and I have confirmed that it's accessible. I also set up entitlements in my project, with applinks URLs specified. In the doc you linked to, the method under how to handle a universal link in iOS and tv
Topic: UI Frameworks SubTopic: General Tags:
Replies
Boosts
Views
Activity
Apr ’25
Reply to TESTFLIGHT: The requested app is not available or doesn t exist
I have the same problem, evem when i build and submit the app with Expo App Services, my app's new build appears in Testflight, but I can't install it: The app is not available or doesnt exist (I translated it from french). However, some of my friends who have an old build on their iPhone can still open it on TestFlight, despite I deleted the old app and builds... I don't understand what is going on tbh.
Replies
Boosts
Views
Activity
Apr ’25
Failed to open URL : Error Domain=NSOSStatusErrorDomain Code=-10814
Regarding the Issue with URL Scheme Not Working。 Hello, our app on the App Store has the following CFBundleURLTypes configuration: We've discovered that the qmkege:// URL scheme is failing to open the app. Steps to Reproduce: 1、We downloaded the installation package from the App Store 2、Entered qmkege:// in Safari, but it fails to launch our app。 The system logs show the following: Key Observation: This issue is not consistently reproducible. In most cases, when we install the app directly from the App Store (without VPN), it works fine. However, the problem occurs when downloading the app through the App Store while connected via VPN. Looking forward to your feedback.
Replies
1
Boosts
0
Views
100
Activity
Apr ’25
Storing metadata alongside files outside of sandbox
Hello all, I'm the developer of REHex, a hex editor which I have been distributing as an app bundle outside of the app store for a few years. REHex allows assigning various bits of metadata (comments, data types, etc) which get stored as filename.rehex-meta alongside the original filename, this works fine when the app is just a standalone bundle, however, when distributed via the app store, sandboxing seems to be mandatory, and there doesn't appear to be any obvious way to get permission to read/write such files. As fallbacks, I've considered adding support for storing the metadata as an extended attribute instead (which breaks compatibility, and won't translate when the file is on a FAT/etc filesystem or network share), or popping up the save/load dialog a second time for the user to select a .rehex-meta file, adding it to the list of whitelisted files for the application (keeps compatibility, but UX is clunky). Are there any ways I can work around this, or perhaps other methods I should consider fo
Replies
5
Boosts
0
Views
187
Activity
Apr ’25
XcodeKit module not found, but why?
I'm working on a plugin, and that target works just fine. I made another target so I can test some computation functions. It doesn't need much from XcodeKit, just some of the structures. I added XcodeKit and Cocoa, but the import XcodeKit just says no such module. If I switch to the plugin target, it's just fine. I've compared both schemes, but I don't see difference which would affect finding the framework.
Replies
2
Boosts
0
Views
131
Activity
Apr ’25
Reply to ASWebAuthenticationSession + https iOS <17.4
If you want a callback URL that starts with https, you must use the .https(...) callback type, which is only available on iOS 17.4 and later. Prior to this, ASWebAuthenticationSession required the use of a custom scheme (i.e. a scheme that's not http/https). For example, your callback URL in that case might look like myapp://auth/callback. Some services may warn against using custom schemes, as they may have security difficulties on some platforms. This is because, unlike https callbacks, any app could claim the myapp:// scheme, potentially resulting in your auth callback going to the wrong app. However, ASWebAuthenticationSession was specifically built to mitigate this concern, ensuring only your app will receive callbacks for that scheme when it's opened via ASWebAuthenticationSession.
Topic: Privacy & Security SubTopic: General Tags:
Replies
Boosts
Views
Activity
Apr ’25
Reply to Issues with Opening iOS Settings from App
The specific settings pages you can navigate to are documented here: Supported URL Schemes. Unfortunately it doesn’t currently include Wi-Fi settings. The latest version of the app_settings Flutter library does seem to document this limitation under AppSettingsType.wifi here: https://pub.dev/documentation/app_settings/latest/app_settings/AppSettingsType.html
Replies
Boosts
Views
Activity
Apr ’25
Reply to App Store Connect
But for some reason, I cannot select a build - Why not? What is stopping you? What happens when you click the plus button and the popup appears with the various builds listed? You're telling us you cannot select a build for some reason, but you don't tell us what's actually happening, so we can't actually help you. Have you added the translations? I think it requires at least one translation, even if it's just English. I think that's in the App Store Localizations bit. Take a look at the Help pages: https://developer.apple.com/help/app-store-connect/ There is a section on Managing Subscriptions.
Replies
Boosts
Views
Activity
Apr ’25
XCode reverts CoreData's .xccurrentversion
I am experiencing an issue where XCode reverts .xccurrentversion file in my iOS app to the first version whenever xcodebuild is run or whenever XCode is started. This means I can build the app and run tests in XCode if I discard the reversion .xccurrentversion on XCode start. However, testing on CI is impossible because the version the tests rely on are reverted whenever xcodebuild is run. The commands I run to reproduce the issue ❯ git status Changes not staged for commit: (use git add ... to update what will be committed) (use git restore ... to discard changes in working directory) modified: Path/.xccurrentversion no changes added to commit (use git add and/or git commit -a) ❯ git checkout Path/.xccurrentversion Updated 1 path from the index ❯ git status nothing to commit, working tree clean ❯ xcodebuild -scheme Scheme -configuration Configuration -sdk iphonesimulator -destination 'platform=iOS Simulator,name=iPhone 16 Pro,OS=latest' -skipPackagePluginValidation -skipMacroValidation
Replies
16
Boosts
0
Views
677
Activity
Apr ’25