I'm building a React Native call application using the following combination of libraries: https://github.com/react-native-webrtc/react-native-callkeep https://github.com/react-native-webrtc/react-native-webrtc https://github.com/react-native-webrtc/react-native-voip-push-notification When I press the speaker button on the call screen displayed by CallKit and change it to ON, the speaker button display on the call screen reverts back to OFF after a few seconds. However, when the speaker button display reverts to OFF, the actual audio output route does not return to the earpiece - the audio continues to output from the speaker without any change. Could you please advise on what cases might cause the speaker button display to revert, and if there are any potential solutions?
Search results for
build disappears
49,429 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
I need to get the app icon from the AppStore Connect API in order to display a list of my apps. However there seems to be no way. I See in the appstoreconnect.apple.com website that the icons are there and available, there is even a function where you can click on it and get the high res version: https://appstoreconnect.apple.com/apps/1504874998/distribution/ios/version/deliverable (this link is of course not available from the outside) I tried builds/{id}/icons which always returns nothing and found an iconAssetToken object in the builds array, but the link is weirdly formatted and leads to nothing. Hope someone can help, I'm fairly new to the API and the usage is quite odd for me so far. Best, Nils
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect API
Tags:
App Store Connect API
Hi @Mattreg, ShazamKit for android 2.1.1 does support 16KB memory page addresses. In branch fix-16k you have correctly imported the latest ShazamKit for android version. I checked this via md5:a6426940b80c4ec5f18a644e4f59193f. As good measure I have also explicitly verified your shazamKit .aar library for 16KB memory compatibility, and I confirm it's 16KB compatible. Steps: unzip the .aar, navigate to the jni folder run (adjust for your environment) ~/android-sdk/ndk/29.0.14033849/toolchains/llvm/prebuilt/darwin-x86_64/bin/llvm-objdump -p libsigx.so | grep LOAD LOAD off 0x0000000000000000 vaddr 0x0000000000000000 paddr 0x0000000000000000 align 2**14 LOAD off 0x000000000005afe0 vaddr 0x000000000005efe0 paddr 0x000000000005efe0 align 2**14 LOAD off 0x000000000005bca0 vaddr 0x0000000000063ca0 paddr 0x0000000000063ca0 align 2**14 2**14 is means it is supporting 16KB pages , see https://developer.android.com/guide/practices/page-sizes. I did also run ~/android-sdk/build-tools/36.0.0/zipalign -v -c -P 16 4
Topic:
Media Technologies
SubTopic:
General
Tags:
So while the first one took 3.5days, the two additional jobs that I submitted during that time all finished at the same time. So it was clearly doing some sort of batch processing. I messed up internal signing so had to restart. New submission took roughly 6 hours. I also submitted a tiny test file which also took the same 6 hours. So again - supports the batch processing theory. Anyways, new build for Intel only took 15 minutes or less. I walked away so the times are definitely improving for me. Just posting the update for others looking into this.
Topic:
Code Signing
SubTopic:
Notarization
Tags:
I'd really like to have a way to integrate with Spotlight in the interim. Understood. I supported Spotlight importers back in the day, and as part of that I created infrastructure to make the whole task easier. I never got around to shipping that as sample code that because I expected CSImportExtension would come online and make it redundant. It seems like I was overly optimistic )-: My code was written in Objective-C, but I spent yesterday converting it to Swift [1]. There are two parts to this: QCFPlugIn — This is a generic mechanism for building different types of CFPlugIn implementations [2]. QSpotlightPlugIn — A type-specific subclass that handles Spotlight. QCFPlugIn.txt QSpotlightPlugIn.txt To use this, subclass QSpotlightPlugIn: private final class MySpotlight: QSpotlightPlugIn { override func importFrom(_ url: URL, type contextTypeUTI: UTType, updating attributes: NSMutableDictionary) throws { … your code here … } } and then invoke the infrastructure from your entry point: @_cdecl(MySpotligh
Topic:
App & System Services
SubTopic:
General
Tags:
I've been trying to add a CoreSpotlight indexer to my macOS application. The new template for the indexer uses the new appex CSImportExtension style importer. I've been following this -> https://developer.apple.com/documentation/corespotlight/csimportextension I changed the CSSupportedContentTypes in the Info.plist file to the correct file type uti. I added a dummy value into the attributes (see code below) - just setting contentDescription to 'noodle' (easy to search for) class ImportExtension: CSImportExtension { override func update(_ attributes: CSSearchableItemAttributeSet, forFileAt: URL) throws { // Add a dummy value, and see whether spotlight finds it attributes.contentDescription = noodle } } I have a number of files on disk that match the uti (and can be found when I search by the file name) Yet, when I build and run my app, the a spotlight search for 'noodle' finds no results. Can anyone give me any advice? I cannot find any indication that the ImportExtension is called (although when I
Hi everyone, I’m an indie developer and recently published our first app on the App Store. It was an exciting milestone, but on April 4, 2025, after the app had been live for about 1–2 weeks and one update had been pushed, we received a notice from Apple stating that our app had been removed from the store and that our developer account is scheduled for termination within a month. Understandably, this was incredibly alarming—but we stayed calm, carefully read through the allegations, and tried to handle the situation with patience and professionalism. The reason given was: App submissions from your account have engaged in concept or feature switch schemes to evade the review process, such as dynamically populating different app content after review, submitting apps with hidden features, repeatedly submitting misleading apps, and/or submitting apps with concrete references to content that you are not authorized to provide or is otherwise not appropriate for the App Store. This was cited as a violation of Secti
Hello everyone, I've encountered an issue with export compliance on App Store Connect that I haven't seen before. In my Info.plist, I have always set the ITSAppUsesNonExemptEncryption key (formerly App Uses Non-Exempt Encryption) to NO. In the past, this was sufficient to bypass the export compliance questions when submitting a build. However, with my most recent submission, I am now being prompted to answer these questions. Nothing has changed in my app's encryption usage. Has there been a recent change in policy or a system-wide issue that would cause this change in behavior? Is anyone else experiencing this? Thank you for your help.
Topic:
Developer Tools & Services
SubTopic:
Apple Developer Program
Hi everyone, we are currently facing an issue with one of our apps regarding the new icon requirements in iOS 26. • We created the app icon using Apple’s Icon Composer. • On the device, everything works perfectly: the app icon is shown on the home screen, and it can also be customized with the new iOS 26 features (colors, transparency, etc.). • However, in TestFlight the app icon is not displayed at all (in the TestFlight app on the device). • In App Store Connect, the icon is also not shown in the overview for the app. Interestingly, within the list of TestFlight builds in App Store Connect the icon is visible. What we have tried so far: • Created an archive and manually uploaded it to App Store Connect → no icon in TestFlight. • Took the working Icon Composer asset from another app target where everything works correctly, deleted the old one in this project, and copied the working asset into the problematic target. → Same behavior: visible on the device, but still missing in TestFlight and App Stor
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
App Store Connect
TestFlight
Icon Composer
Started a new X-Code Project after updating to 26.0.1 and realized that I get an error when trying to mark a class as ObservableObject => Class XYZ does not conform to Protocol 'ObservableObject'. Strange behaviour, because at old projects the code is working even though the build options are the same and other settings like iOS version in Target are the same. There must be something chaged under the hood of XCode? I have to import Combine now, before I could write my class, e.g. CoreData Datamanager: ObservableObject only using CoreData.
Well, that’s interesting. I again tried replicating this problem and everything worked for me. But then I tried again in an macOS > App target and I did see the problem. At that point I started digging… It turns out that I made a mistake in my previous post: [quote='860660022, DTS Engineer, /thread/802686?answerId=860660022#860660022'] I created a new project from the macOS > Command Line Tool template. [/quote] I didn’t use the macOS > Command Line Tool template, but rather I used my own personal template. Once I retesting with the built-in macOS > Command Line Tool template, I saw the problem immediately. And that give me a working and a non-working case to compare. And doing that I found that this behaviour is gated by the Member Import Visibility build setting. That’s set in the built-in template and not set in my personal template. And with it set I see the error compiling DataController and with it unset I don’t. This build setting is a product of a recent Swift Evolution c
Topic:
App & System Services
SubTopic:
Processes & Concurrency
Tags:
These are the two cases I’ve tested (with screenshots attached): • First screenshot: Building for iPhone — import DeclaredAgeRange works fine. • Second screenshot: Building for Mac (Catalyst) — import DeclaredAgeRange fails with a module import error.
Topic:
App & System Services
SubTopic:
General
This is clearly a bug. We either need to fix the SDK or fix the docs. I encourage you to file a bug to that effect. Please post your bug number, just for the record. You’ll be able to get your code building by conditionalising it like so: #if canImport(DeclaredAgeRange) import DeclaredAgeRange #endif And likewise for the places you use the API. Still, that leaves you without this functionality )-: Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic:
App & System Services
SubTopic:
General
I tried to create a new IOS provisioning profile and re-apply it to the app using Xcode to build it, but I got into trouble. The build is good, but it bounces when running the app. I would appreciate it if you could let me know what to do.
I built a TestFlight version of my unpublished app. While using it, I wanted to test out the subscription purchase and when I did, I used my real production Apple ID and not a Sandbox test account to purchase the subscription. I was surprised to see that it worked and I was able to use the test subscription in the app. However, I now have no way of canceling it. It has renewed every day at the same time due to the accelerated TestFlight subscription rate (it's a monthly sub). I read that it should stop auto-renewing after the 6th time, but I believe it's been over a week now and it still hasn't cancelled. I understand that it's not a real purchase, but I would still like to cancel it so I can try it without the purchase again using this account and also use it with a different Sandbox account. Can someone help me with canceling it? Since the account I used was not a Sandbox account, I can't just clear the purchase history in App Store Connect. Also, I can't go into my personal account settings to remove the s