“iPhone 16 pro”

[quote='878607022, Nickkk, /thread/817724?answerId=878607022#878607022, /profile/Nickkk'] I'm assuming that's what you mean by Mach-O image. [/quote] A Mach-O image is code that can be mapped into memory by the dynamic linker and then run directly, as opposed to something like a .o file that contains code that must be linked before it can be run. I talk more about this in An Apple Library Primer. A Mach-O image is often stored within a universal binary, one image per architecture. So when looking at stuff like this you have to consider the image of the architecture that was running. The other thing to considered is that the dynamic linker may only map in parts of your image. A good way to see what actually gets mapped is to run the app and then run vmmap against it. Consider this: % ls -lh Pages Creator Studio.app/Contents/MacOS/Pages -rwxr-xr-x 1 root wheel 45M 16 Jan 02:44 Pages Creator Studio.app/Contents/MacOS/Pages The Pages executable is 45 MiB. And this: % file Pages Creator Studio.app/Content

thanks everyone for your responses! i didn’t realized that someone else who also has access to the developer account had uploaded screenshots in the iPad section that had alpha channel issues. my whole gaze was on iPhone screenshots; those were the ones i uploaded myself. apparently the failed iPad screenshots upload deterred the submission the whole time. apple could do better w pointing specifically where an error is coming from btw :(

pretty much same issue, OSX / apple watch version 26.3. Developer mode does not show on apple watch settings Apple watch does not show as available in Xcode even if paired to an iphone connected to Mac via USB-c

I've been waiting since the 5th of February - it's literally destroyed our momentum and the complete radio silence is totally unacceptable (one 'automated' reply after 2 weeks) - it appears there is nothing I can do to affect this process (at least through their recommended channels - phone support is a waste of time... nice people, but zero influence). I'm not exaggerating when I say I feel totally helpless here. I've never experienced service quite like this. The fact I'm paying for it, beggars belief!!!

You are not alone! We are having the exact same issue - we've been waiting for over 4-weeks with zero movement, and nothing to suggest anything is likely to change. Phone support has no oversight or influence and I waited over 2 weeks for an 'automated' reply to my support request email (essentially telling me to be patient, and that they're dealing with a large amount of submissions). I'm not sure what to do... Every day that passes is momentum/money/time/enthusiasm lost. It's truly upsetting! Android turned it around in 3 days - I hope for both our sakes that something changes soon! All the best

Are there any other solutions for this? I still can't update to beta 3 (M1 Pro). I've tried all the ideas I've seen so far :( Update: I figured out the issue; it was the real time virus scanner. So the install was successful.

Same issue here. It started about 24 hours ago and I haven’t found a solution yet. Things I have already tried: • Rebuilding the app multiple times via GitHub Actions • Regenerating certificates / Match secrets • Waiting 24 hours after upload • Deleting the app and reinstalling • Deleting and reinstalling TestFlight • Restarting the phone multiple times • Verified I’m assigned to the internal tester group in App Store Connect • Confirmed the build status is Complete in App Store Connect The build installs and runs on my phone, but when I open the app page in TestFlight it shows “Couldn’t Load App – TestFlight is currently unavailable.” Also noticing the Apple Watch companion app will not install (stuck installing).

Creating a custom Wallet pass, especially one intended to display a simple vertical layout of an address, can be a bit tricky due to the constraints and specific formatting requirements of Apple's Wallet Pass format. Based on the JSON you've provided, here are some steps and considerations to help you achieve the desired layout: Key Considerations Field Configuration: The primaryFields and auxiliaryFields in your JSON are used to display information on the pass. For a simple address layout, you might want to creatively use these fields. Text Styling: Wallet passes have limited styling options, but you can control the font size, weight, and color to some extent using the textStyle attribute in fields. Layout Adjustments: Since Wallet passes don't support arbitrary layouts, you'll need to fit your content into the available fields and styles. You might need to compromise on the exact layout you envisioned. JSON Adjustments Here's an adjusted version of your JSON that attempts to create a vertical address layout

It is still an issue on iPadOS 26.3.1. While it works on and iPhone with iOS 26.3.1 like pre 26, the initially described problem does still exists on an iPad with 26.3.1.