same here. I never noticed that it was stuck on wireless debugging and wondered why it'd take a minute to start the damned thing, or 3 or 4 seconds per step in the debugger. My solution was to simply restart the iPhone while connected. I have to do that from time to time but I gladly spend 1 minute every couple of hours instead of losing the 15 minutes or more per hour just waiting....and w a i t i n g.......
missing package product
42,955 results found
Post
Replies
Boosts
Views
Activity
I could not push to the App Store in the organizer (only 'custom' available under 'method for distribution', then I can only select 'Built Products' or 'Archive', no upload to App Store, see screenshot) This issue occurs when you have a generic archive. For more information, see TN3110: Resolving generic Xcode archive issue. Is what I am trying even possible, or do the main app and app clip need to be published in the same XCode project? When you submit an App Clip for distribution to testers with TestFlight or for publishing in the App Store, you don’t submit the App Clip on its own; you export and submit the app bundle of the full app that includes the App Clip. For more information, see Distributing your App Clip.
Hello, thanks for you reply! As I've said, the crashes above have been received on our crash reporter from our Safari App Extension which is running in production on our users' machines. I haven't been able to reproduce any crash locally on my machine. Also, I just suspect that the crashes and the No context logs are the same issue, but I don't know this for certain. With that in mind, I sent a bug submission through Feedback Assistant about this. The submission includes 30 user crashes (from the crash reporter service) that may be relevant, but no crashes from my machine. I've also added a few screenshots. The feedback submission number is FB14156523.
Hi there! you're missing a closing bracket after Text(Home), so it is only rendering the first tab since it never sees an end to the tab item.
Hi! I know this post is more that 6 months old, but I'm facing the same issue and wondering if there has there been any development on this? After rolling out some security features using attestation on our app into production, we have been observing the same strange occurrences that @mahashis described and from our logs we could extract some metrics that place the total percentage of affected users in the 5% to 6% of all users using the app, amounting to above ten thousand installations. Even though it is expected some failures to happen like it is mentioned in the docs and in the comment above from @endecotp (for users migrating devices) and actual unsecured (example: jailbroken?) devices, it's hard to credit that is the case for so such a high percentage of users. Even more so because it happens when attesting a freshly generated key which typically (and per documentation advice) only happens on fresh installations of the app or when a key is reported as invalid from the DCAppAttest service api. T
DevForums is a place for third-party developers to get technical help when building products for Apple platforms. Indeed it is. So, DID John Daniel get technical help here when he was building his 'EtreCheck' product. Did Apple TEST the product before permitting it to be sold in the Apple App Store some years ago? Please advise. Thanks.
If I have a main app with several different Reality Composer pro packages with all their AR/VR assets, how can I enable ODR (on-demand resource tags) on them? I can't find a way.
Hello, I have an application that includes In-App Purchases (IAP). Previously, I offered a non-consumable lifetime premium option. With my latest update, I added a monthly subscription option. I prepared and implemented the subscriptions correctly and submitted the app update, expecting both the app update and the subscriptions to be reviewed together by the same reviewer. However, my app update was approved while the subscriptions were rejected. Now, my app is live but only offering the original IAP, which includes the non-consumable lifetime premium option and the new monthly subscription. Guideline 3.1.1 - Business - Payments - In-App Purchase We have begun the review of your in-app purchases but aren't able to continue because your submitted in-app purchases indicate a change of business model for your app. Specifically, your existing Non-Consumable business model has changed to include a auto-renewable subscription in-app purchase business model type. Therefore, we need to verify the implementation of yo
Hello! I was wondering if any other developers are experiencing issues with accessing the web extension background script console, sources, etc. on the latest Safari Technology preview or macOS Sequoia betas. We have an extension which has a persistent background script. In the latest public release of Safari version 17.5 (19618.2.12.11.6) on macOS Sonoma, everything works as expected. When I enable developer mode in Safari, it shows an additional Develop menu and when I select Web Extension Background Content in the dropdown, it shows a list of background pages for all installed extensions. Attaching a screenshot for reference. However, if I install the latest Safari Technology Preview 197 on macOS Sonoma or just test with the Safari version that comes with MacOS Sequoia beta 1 or beta 2, the Web Extension Background Content dropdown menu does not list any background pages. Attaching a screenshot for reference. We started discussing the issue with Apple during the latest WWDC. If anyone at Apple sees this po
Basically, in my widget/live activity, I want to extract reusable views into a separate file with an isolated view and preview. Dummy example below. I cannot do it because it says missing previewcontext. The only way I've found is to add the view to my main app target, but I don't want to clutter my main app wiews that only exist in my widgets if I can avoid it. Can this be done somehow? Thoughts appreciated. Dummy example (tried with and without previewLayout: struct StatusActivityView: View { let status: UserStatusData var body: some View { VStack(alignment: .center) { Text(Dummy example) }.background(.blue).padding(5) } } @available(iOS 16.2, *) struct StatusActivityView_Previews: PreviewProvider { static var previews: some View { let status = WidgetConstants.defaultEntry() return StatusActivityView(status: status).previewLayout(.sizeThatFits) } }
This still happens in iOS17. anyone know a solution or a workaround? We cant be resetting the environment in production.
For me, the error was first observed when running late IOS17 levels. If you look at the URL, the path is missing the host component from the URL resulting in a string for the url of file:///System/Library/CoreServices... which is an invalid URL construct due to a missing host component after the file://. That is why you are seeing the error. The path you are seeing in the URL is on the Mac system driving the App on the iPhone and that path does not exist on the iPhone device. I have been trying to track down component that it originaties in. Ir you take a demo application and step through the AppDelegate.swift from the entry point, you get the error on the execution of the second line of the AppDelegate class initialization on the line that starts var window. It consistently stops with the execution of that line. @main class AppDelegate: UIResponder, UIApplicationDelegate { var window: UIWindow? func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIAp
Hi, mac 14.4 M1 Chip. I can successfully create the utun interface by call out the exec via sudo. the c code for this looks like this. #include #include #include #include #include #include #include #include #include #include #include #include #include #include #define UTUN_CONTROL_NAME com.apple.net.utun_control #define UTUN_OPT_IFNAME 2 int create_utun_interface(char *ifname) { int fd = socket(PF_SYSTEM, SOCK_DGRAM, SYSPROTO_CONTROL); if (fd < 0) { perror(socket(PF_SYSTEM, SOCK_DGRAM, SYSPROTO_CONTROL)); return -1; } struct ctl_info ctlInfo; memset(&ctlInfo, 0, sizeof(ctlInfo)); strncpy(ctlInfo.ctl_name, UTUN_CONTROL_NAME, sizeof(ctlInfo.ctl_name)); if (ioctl(fd, CTLIOCGINFO, &ctlInfo) == -1) { perror(ioctl(CTLIOCGINFO)); close(fd); return -1; } struct sockaddr_ctl sc; memset(&sc, 0, sizeof(sc)); sc.sc_id = ctlInfo.ctl_id; sc.sc_len = sizeof(sc); sc.sc_family = AF_SYSTEM; sc.ss_sysaddr = AF_SYS_CONTROL; sc.sc_unit = 455; // Let the kernel choose a unit for us. if (connect(fd, (st
I would honest never suggest anybody to use any developer beta unless they have a buffer model to handle the bugs that it will have. They are the earliest versions of the new OS designed for developers to test their applications within the new environment as early as possible. Using this on a primary device introduces bugs, security vulnerabilities, potential data loss, and some users even report a degradation in their battery health due to the OS not being optimized for general production. A friendly warning to anybody who might potentionally see this before updating.
Hi. I have developed a PWA and built it with PWABuilder.com. My PWA is already working and published in Google Play Store. PWABuilder is able to create iOS packages and I was wondering if PWAs are allowed in Apple's App Store. Does anyone have ever published a PWA to the App Store of know if it is allowed? Thanks in advance.