Search results for

missing package product

51,800 results found

Post

Replies

Boosts

Views

Activity

URGENT: App & Developer Name completely missing from Search Index (2.5 weeks live, 2k+ DLs)
Hi there, I’m writing this because I’m feeling incredibly frustrated and downbeat. I launched my app about two and a half weeks ago, and while it’s been a success in terms of users—with over 2k downloads and 35 five-star reviews via Reddit—it is currently invisible when searched for on the App Store (it can be found by direct link or Google search). Even when searching for the exact app name or my developer name (Robert Lothian), nothing comes up. It’s as if the app doesn't exist in your search database. To make matters worse, the app was featured in several articles, podcasts, and live streams last week. Because of this search issue, potential users who heard about the app couldn't find it. This has not only stunted my growth during a critical launch window but I fear it is causing genuine damage to my reputation as a developer. I raised a ticket last Saturday (102811242184) but haven't heard anything back, I just did a follow-up ticket just now, as it has been a week. I truly believe this is a backend synch
0
0
159
3w
Reply to String Catalog stops updating upon changing source code
Thanks for the post. It seems like you have not received any replies. I think I have a suggestions for you to get people to see the issue you encountering by providing a little project sample. I am not aware of any localization issues at this time. So once that string is translated, changing the default value in code and rebuilding does not update the catalog? Or is there a way to determine what strings have default values in code that do not match the catalog values to see if any were missed as wording was tweaked over time? It’s been a long time since I use that, when I was using it I did periodically export my localization files using Xcode's Editor > Export for Localization.... This created an XLIFF file that I can diff against previous versions to spot discrepancies between default values in code and your localization files. Now, I think many developers are experts in localization and they can provide you great suggestions but I think that if you provide a little focused sample that shows in
3w
Reply to HomePod mini temperature sensor in HomeKit with Mac Catalyst
Aha, I see. I (along with the OP, it seems) got misled by the fact that they are presented through the Home application (but of course, I can see there's no reason why Home could/should not use different and probably private APIs to communicate with these, aside from its primary task to present and control the HomeKit). Keep in mind that HomePods (like AppleTVs) are HomeHubs, so there's already a control channel (either direct or over iCloud) that's relaying data between the device you’re running Home.app on and the HomePod. So the data is actually moving through that existing channel, not being sent on its own. To a large extent, that's also why the temperature sensor feature exists at all— it's not that we thought there was some great demand for integrated speaker/thermometers, it's that all of the most complicated work had already been done as part of HomeHub. Oh, I did not; I regret to admit I had considered “whatever one might want to do with all the other HomeKit temperature sensors should be possible w
Topic: App & System Services SubTopic: Hardware Tags:
3w
String Catalog stops updating upon changing source code
If you add a new string in your app (for example String(localized: contact_support_message, defaultValue: Please contact support)), then later you change that default value and rebuild, the string catalog updates to match as expected. But once that string is translated, changing the default value in code and rebuilding does not update the catalog. You seemingly have to go manually change the default value for English in the catalog to match the code (which marks the translation as Needs Review). Is there a better way? Or is there a way to determine what strings have default values in code that do not match the catalog values to see if any were missed as wording was tweaked over time?
3
0
143
3w
Reply to MetalToolchain download fails on macOS 26.2, build 17C48 catalog error
xcodebuild: error: Failed fetching catalog for assetType (com.apple.MobileAsset.MetalToolchain), serverParameters ({ RequestedBuild = 17C48; }) This can indicate a network-level error reaching Apple's servers. By chance, is your device or network managed by an IT department? I ask because some enterprises use the information in Use Apple products on enterprise networks to configure devices or the overall enterprise network to meet the needs of the enterprise, but that may be in conflict here with getting the Metal toolchain. If you run the following commands in Terminal, what do you get as a result? % curl -v https://gdmf.apple.com % curl -v https://download.developer.apple.com % curl -v https://devimages-cdn.apple.com If you get an HTTP result (even if it's a 404), that's good, because it means your Mac could reach that server to get an HTTP code. But if you get a different message like a failure to connect, then that indicates something is interfering with your Mac's ability to reach Apple's servic
3w
Reply to Unknown APNs ERROR: BadEnvironmentKeyInToken when sending Push To Talk notifications
Hi, I'm experiencing the exact same issue with BadEnvironmentKeyInToken (HTTP 403) from APNs. In my case: I'm using a P8 key (not certificate-based auth) The P8 key was recently created with APNs service enabled Everything works fine with sandbox/development environment (Debug builds via Xcode) The error only occurs with production environment (TestFlight builds) My provisioning profile correctly shows aps-environment: production The device token is valid for production (confirmed by the profile) The strange part is: Sandbox server (api.sandbox.push.apple.com): Returns BadDeviceToken (expected, since token is for production) Production server (api.push.apple.com): Returns BadEnvironmentKeyInToken (HTTP 403) My JWT generation looks correct (same key works for sandbox), Team ID, Key ID, and Bundle ID are all verified to be correct. Did you ever find a solution to this issue?
3w
Reply to SwiftUI view state resetting after alert is shown
Thanks for chiming in @lucasgladding! The package dependency is actually the code that we are working on. We want the integration point to be simple within the apps that uses our package. It's true that moving the sheet up in the view layout does correct the behavior but that complicates the app side integration. Since it seems to be new behavior, and currently only reproducible on certain simulators, it feels like a bug. A feedback request (FB21697975) was submitted through Feedback Assistant to Apple. In our use case, the alert is a sign out confirmation alert, so having it auto dismiss creates a bad user experience and would be problematic if it started happening on devices
Topic: UI Frameworks SubTopic: SwiftUI
3w
IAP stuck in Review causing rejection
I’m stuck in a loop where my in-app purchase (IAP) product cannot be reviewed because my app version is in “Rejected” status. In order to submit the IAP for review, I need to submit a new app version and select the IAP product. But since the current version is rejected, I can't select the IAP during submission. As a result, RevenueCat can't fetch the IAP products, and the app appears to not use in-app purchases, which leads to another rejection. I’d like to know the correct steps to break this cycle and properly submit both the app and the IAP for review. Any guidance is appreciated!
1
0
205
3w
Reply to Invoking app clip, that was installed from TestFlight, from a different app.
No, you don't need an HTML page with the app-clip-bundle-id meta tag to fix URL invocation (Notes app or UIApplication.shared.open(url)) for TestFlight App Clips. This meta element is for production web/Safari invocations to trigger the card preview; TestFlight restricts dynamic URL taps/open calls despite green Domain Status and approved swcutil (Site/Fmwk Approval: approved). QR/Local Experience works because it bypasses these limits via explicit developer override. TestFlight Limitations Apple docs confirm TestFlight prioritizes controlled testing: Direct launch from TestFlight app (no card, loads clip). QR/NFC with Local Experience (full card flow). Arbitrary URLs (Notes, other apps) intentionally unsupported to mimic beta safety. Your AASA is perfect appclips entry + /numverify/appclip/* components match, CDN-propagated, swcutil validated. Your Options Method Works for Card+Launch? Setup TestFlight Invocations Partial (testers launch via TF UI) App Store Connect > TestFlight > Build > A
3w
Reply to Non-consumable IAP app rejected: Pro auto-unlocked for pre-1.0.5 paid users, App Review asks for expired subscription account
Follow-up / Update Update: New rejection – “Unlock Pro not responsive” on iPad, cannot reproduce locally I wanted to provide an update, as the app was rejected again after addressing the previous feedback. New rejection details Apple now reports the following issue: Guideline 2.1 – Performance – App Completeness Bug description: “Unlock Pro is not responsive” Steps to reproduce (per review): Tap “Unlock Pro” No action occurs Review device: iPad Air (5th generation) OS: iPadOS 26.2.1 This is confusing because: The app works correctly on my devices I tested the full purchase flow successfully: on physical iPhone in the iOS Simulator even on an iPad simulator The StoreKit purchase sheet appears as expected when tapping “Unlock Pro” I followed Apple’s advice to: uninstall previous versions reinstall fresh test upgrade paths I still cannot reproduce a state where tapping “Unlock Pro” does nothing. Important technical detail (possible cause) Looking closer at my implementation, I realized there is a silent-failure
Topic: App & System Services SubTopic: StoreKit Tags:
3w