I have a strange problem. My code works perfectly on my iPhone, i.e. on a real iPhone, but when I upload the build version to TestFlight, it no longer works. I use React Native. The issue is as follows: I have created a code for Grid View that runs automatically when another person joins the stream. It works locally without any problems, but unfortunately the public version does not work. What could be the reason for this?
Search results for
build disappears
49,247 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
Device: iPhone 15pro, ios26.0 (23A 341) IOS version: 26.0 (23A 341) When using position: sticky; bottom: 0, the div is expected to stick to the bottom of the viewport when the browser toolbar hides while scrolling. However, it stops at the height where the toolbar was, instead of moving down with the disappearing toolbar. In the image below, the red-bordered navigation shows the situation where it does not stick to the bottom. i
Thanks for the extra info. Where did this “modeling tool” come from? Is it something you created? Something you got from a vendor? Or an open source thing you’re building? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic:
App & System Services
SubTopic:
Networking
The more obscure your app or system extension, the more important it is to lean into the system log. Logging to stdout is fine for simple things, but once you start building a complex product you usually run into some case where you can’t see such output. Moreover, you can never see such output once you ship your product, which makes it much harder to debug problems that only show up in the field. So, my advice here is that you use this as an opportunity to switch over to the system log. It’s easy to use, has many great features, and your log entries will be visible regardless of the context. See Your Friend the System Log for lots of hints and tips on this front. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic:
App & System Services
SubTopic:
Core OS
Tags:
I’d like to clarify your overall goal here. Are you planning to ship an app based on Chromium? Or are you building some sort of plug-in that you install within Chromium? This matters because… [quote='800879021, poluyanov, /thread/800879, /profile/poluyanov'] simply overwriting files in the app bundle [/quote] Right. That breaks the seal on the code signature, which causes problems for all privacy subsystems, which rely on the code signature to track the identity of your code, that is, to determine that version N+1 of your app is the ‘same code’ as version N. This is something we call out in TN3179 Understanding local network privacy: To ensure that local network privacy reliably tracks the identity of your macOS program, sign it with an Apple-issued code-signing identity. Most apps don’t suffer from this problem because, when Xcode rebuilds the app, it signs result. If you’ve selected an Apple-issued code-signing identity, the new app has the same designated requirement as the previous app, and thus
Topic:
App & System Services
SubTopic:
Networking
Tags:
@DTS Engineer What is your minimum deployment target set to? minimum deployment target set to 1 This is also an issue — that's a static library. .a files should never show up in a final app bundle, because their contents has been linked into some other binary during the build process. How can I integrate a static library (.a file) into an iOS app so that it does not appear in the final app bundle? Currently, I have defined a .podspec file and installed it via pod install.
Topic:
App Store Distribution & Marketing
SubTopic:
TestFlight
What is your minimum deployment target set to? All of these libswift* files should no longer be included. They were necessary for compatibility purposes on iOS versions prior to Swift being built into iOS directly, which is long past now. 14221248 09-16-2025 10:33 Payload/Runner.app/Frameworks/libAudioFeature.a This is also an issue — that's a static library. .a files should never show up in a final app bundle, because their contents has been linked into some other binary during the build process. — Ed Ford, DTS Engineer
Topic:
App Store Distribution & Marketing
SubTopic:
TestFlight
The below code will render a list of items and a button to shuffle them and change their height withAnimation. If you scroll down and shuffle it you will eventually see glitches in the animation, mostly consisting of ghost items animating on top of other items and disappearing. Does anyone know why this is happening, and how to stop it happening? The issue goes away entirely if I use a VStack, but using a VStack brings its own problems. import SwiftUI struct Item: Identifiable { let id = UUID() var height: CGFloat var label: String } struct ContentView: View { @State private var items: [Item] = (0..<30).map { i in Item(height: .random(in: 80...220), label: Row (i)) } var body: some View { NavigationStack { ScrollView { LazyVStack(spacing: 8) { ForEach(items) { item in Text(item.label) .frame(maxWidth: .infinity) .frame(height: item.height) .background(.gray.opacity(0.15)) .clipShape(RoundedRectangle(cornerRadius: 12)) .padding(.horizontal) } } .padding(.vertical) } .navigationTitle(LazyVStack Demo
On iOS when I run my Autofill extension target from Xcode and attach to Safari, Swift print() statements appear in the Xcode console log. If I run the same extension on MacOS Sequoia, no log messages appear. The header strip in the debugger area remains blank. Anyone know how to see these log messages? In both cases, the scheme is set to Debug build, and Debug Executable is not selected. In fact, for iOS the Debug Executable is grayed out. When I set Debug Executable on the MacOS run, I get failure to attach with a warning about permission to debug Safari.
Hello, I’m seeing a layout issue where the system window controls overlap the navigation bar’s right-side buttons when the app window is resized on iPadOS 26. Environment Xcode: 16.4 Simulator: iPadOS 26.0, device profile iPad Pro 13-inch Physical device: iPad updated to iPadOS 26 (same behavior) UI stack: UIKit + Storyboards (no SwiftUI) App structure: Root UINavigationController Summary Since iPadOS 26 introduced freely resizable app windows, the system’s window management controls (close/minimize/resize at the top-right) begin to overlap the navigation bar buttons as the window size becomes smaller. At maximum window size there’s no issue. Additionally, the navigation bar buttons themselves appear to scale down visually when the window gets smaller. Steps to Reproduce Build with Xcode 16.4 and run on iPadOS 26.0 (simulator or device). Open a screen embedded in a UINavigationController with right-side bar button items. Resize the app window to a smaller size. Observe the top-right system window con
I've made a dext and a user client that overrides IOUserSCSIPeripheralDeviceType00, with the object of writing device firmware to the driver. I can gain and relinquish exclusive access to the device, I can call UserReportMediumBlockSize and get back a sensible answer (512). I can build command parameters with the INQUIRY macro from IOUserSCSIPeripheralDeviceHelper.h and send that command successfully using UserSendCB, and I receive sensible-looking Inquiry data from the device. However, what I really want to do is send a WriteBuffer command (opcode 0x3B), and that doesn't work. I have yet to put a bus analyzer on it, but I don't think the command goes out on the bus - there's no valid sense data, and the error returned is 0xe00002bc, or kIOReturnError, which isn't helpful. This is the code I have which doesn't work. kern_return_t driver::writeChunk(const char * buf, size_t atOffset, size_t length, bool lastOne) { DebugMsg(writeChunk %p at %ld for %ld, buf, atOffset, length); SCSIType00OutParameters o
Hi everyone, Complete newbie here. Building an app and trying to use Cloudkit. I've added the CloudKit capability, triple checked the entitlements file for appropriate keys, made sure the code signing entitlements are pointing to the correct entitlements file. I've removed and cleared all of those settings and even created a new container as well as refreshed the signing. I just can't seem to figure out why I keep getting this error: Significant issue at CKContainer.m:747: In order to use CloudKit, your process must have a com.apple.developer.icloud-services entitlement. The value of this entitlement must be an array that includes the string CloudKit or CloudKit-Anonymous. Any guidance is greatly appreciated.
I have previously referred to PTPPassThrough, but there is no example of sending the outData parameter, and I have not found it on Apple forums or online. So, I did find some test code of ours that does use outData. I can't directly provide the code, as it's part of a multi-layer architecture which means that code can't easily be provided. However, what I can say is: The way you've built out the structure generally appears correct. Every operation we send has type set to 1. It's actually hard coded into the method that builds out USB data packet. Nothing special is done to handle outData. The data object is built out as a separate data object and then included with the request. Finally, on the actual command you're sending, I don't know what the command format for 0x9205 actually is, but I don't think this is correct: unsigned char specialData = 1; NSData sendData = [NSData dataWithBytes:&specialData length:1]; As far as I can tell, the main reason the extra data approach is used is to provide a
Topic:
App & System Services
SubTopic:
Hardware
tried to restore purchase Are you calling restoreCompletedTransactions() to restore your purchases? If yes, this method doesn't return in the following situations: All transactions are unfinished. The user did not purchase anything that is restorable. You tried to restore items that are not restorable, such as a non-renewing subscription or a consumable product. Your app’s build version does not meet the guidelines for the CFBundleVersion key.
Topic:
App & System Services
SubTopic:
StoreKit
Tags:
@seanodonnell , @ToniMC Thank you for your Feedback reports. Please update your reports with a link to your failing build so our team can investigate the issue.
Topic:
Developer Tools & Services
SubTopic:
Xcode Cloud