Cannot download FCPX that was purchased few yerars ago on Macbook pro with Tahoe OS beta. App do not show on my downloaded apps

Hi everyone, I’m developing an app for managing internet services, which includes features like controlling modems, paying internet bills, purchasing internet packages, buying cameras, subscribing to FSafety (modem management), UltraFast (boosting internet speed for gaming), and selling health-related devices like blood glucose monitors, as well as other telecom-related products. I have some questions about Apple’s review process and payment policies: Do features like paying internet bills, buying internet packages, purchasing cameras, subscribing to FSafety and UltraFast violate any of Apple’s policies (App Store Review Guidelines)? If my app doesn’t violate any policies, how would Apple charge for these transactions, and what is the fee structure? If I use an external payment gateway (not Apple’s) for transactions like paying bills or buying products, would I need to provide additional documentation for my app to be approved on the App Store? What is the review process for apps with external payment features? Is there anything special I need to do when submitting the app to the App Store? I would appreciate any insights from those who have experience with developing apps that include payment functionality. Thanks so much!

HAVE ANY ONE EXPERIENCE PASS KEY DEVICE PROMPTS RANDOMLY ON BETA IOS SOFTWARE >?

So, I started with the developer beta on Tahoe a couple months ago. I gave the new Apps.app a fair shot.... I HATE it. Finally used a terminal work around to get Launchpad back up and running. Now with the release of the Public Beta and Developer Beta 5, Apple has nerfed the Launchpad.app altogether. Apple, listen to your customers. Yes some people really love spotlight but not everyone wants to scroll through a list of apps as long as my leg because, my PTSD brain won't let me remember the name of the app to type into spotlight. The Launchpad app had a great visual reference for those of us with poor memory function. Bring it back, and let your customers choose which one they want to use.

Mac users often ask whether they should install "anti-virus" software. The answer usually given on ASC is "no." The answer is right, but it may give the wrong impression that there is no threat from what are loosely called "viruses." There is a threat, and you need to educate yourself about it. This is a comment on what you should—and should not—do to protect yourself from malicious software ("malware") that circulates on the Internet and gets onto a computer as an unintended consequence of the user's actions. It does not apply to software, such as keystroke loggers, that may be installed deliberately by an intruder who has hands-on access to the computer, or who has been able to log in to it remotely. That threat is in a different category, and there's no easy way to defend against it. The comment is long because the issue is complex. The key points are in sections 5, 6, and 10. OS X now implements three layers of built-in protection specifically against malware, not counting runtime protections such as execute disable, sandboxing, system library randomization, and address space layout randomization that may also guard against other kinds of exploits. 2. All versions of OS X since 10.6.7 have been able to detect known Mac malware in downloaded files, and to block insecure web plugins. This feature is transparent to the user. Internally Apple calls it "XProtect." The malware recognition database used by XProtect is automatically updated; however, you shouldn't rely on it, because the attackers are always at least a day ahead of the defenders. The following caveats apply to XProtect: ☞ It can be bypassed by some third-party networking software, such as BitTorrent clients and Java applets. ☞ It only applies to software downloaded from the network. Software installed from a CD or other media is not checked. As new versions of OS X are released, it's not clear whether Apple will indefinitely continue to maintain the XProtect database of older versions such as 10.6. The security of obsolete system versions may eventually be degraded. Security updates to the code of obsolete systems will stop being released at some point, and that may leave them open to other kinds of attack besides malware. 3. Starting with OS X 10.7.5, there has been a second layer of built-in malware protection, designated "Gatekeeper" by Apple. By default, applications and Installer packages downloaded from the network will only run if they're digitally signed by a developer with a certificate issued by Apple. Software certified in this way hasn't necessarily been tested by Apple, but you can be reasonably sure that it hasn't been modified by anyone other than the developer. His identity is known to Apple, so he could be held legally responsible if he distributed malware. That may not mean much if the developer lives in a country with a weak legal system (see below.) Gatekeeper doesn't depend on a database of known malware. It has, however, the same limitations as XProtect, and in addition the following: ☞ It can easily be disabled or overridden by the user. ☞ A malware attacker could get control of a code-signing certificate under false pretenses, or could simply ignore the consequences of distributing codesigned malware. ☞ An App Store developer could find a way to bypass Apple's oversight, or the oversight could fail due to human error. Apple has so far failed to revoke the codesigning certificates of some known abusers, thereby diluting the value of Gatekeeper and the Developer ID program. These failures don't involve App Store products, however. For the reasons given, App Store products, and—to a lesser extent—other applications recognized by Gatekeeper as signed, are safer than others, but they can't be considered absolutely safe. "Sandboxed" applications may prompt for access to private data, such as your contacts, or for access to the network. Think before granting that access. Sandbox security is based on user input. Never click through any request for authorization without thinking. 4. Starting with OS X 10.8.3, a third layer of protection has been added: a "Malware Removal Tool" (MRT). MRT runs automatically in the background when you update the OS. It checks for, and removes, malware that may have evaded the other protections via a Java exploit (see below.) MRT also runs when you install or update the Apple-supplied Java runtime (but not the Oracle runtime.) Like XProtect, MRT is effective against known threats, but not against unknown ones. It notifies you if it finds malware, but otherwise there's no user interface to MRT. 5. The built-in security features of OS X reduce the risk of malware attack, but they are not, and never will be, complete protection. Malware is a problem of human behavior, and a technological fix is not going to solve it. Trusting software to protect you will only make you more vulnerable. The best defense is always going to be your own intelligence. With the possible exception of Java exploits, all known malware circulating on the Internet that affects a fully-updated installation of OS X 10.6 or later takes the form of so-called "****** horses," which can only have an effect if the victim is duped into running them. The threat therefore amounts to a battle of wits between you and the scam artists. If you're smarter than they think you are, you'll win. That means, in practice, that you always stay within a safe harbor of computing practices. Malware defence By Linc Davis - https://discussions.apple.com/thread/6460085

Ok, so I’ve downloaded iOS 26 for the iPhone and iPad and there are a couple of points bugging me. Why oh why would somebody think that it was a good idea to remove the ability to scroll through photos in a folder in files? Where in their tiny minds did they think that opening a photo, viewing said photo, then closing photo to then open the next photo in sequence was a better or more productive way than just swiping left and right? I mean, seriously!!! And why the need for a separate Preview app when it worked fine opening files in the Files app?! I deleted the Preview app from my iPhone to see what difference it would make, but alas it made things worse. Now, because there’s no Preview app, Files wants to open my photos in an image editing app called Afterlite! I checked settings for the files app, and the only options I have for opening photos are Afterlite (which it’s decided to make default), the Photoshop app, or iMovie! Does anyone have any ideas how to get photos stored in the Files app to open IN the Files app or at least the Photos app? Just when I thought they’d come to their senses and sorted out that god awful iOS 18 Photos app, they go and do something like this! Also, can someone explain to me what the point is of having a month and year view in the Photos app? When I sort by month and pick a particular month or date in a month, instead of showing just those images taken that month, it just takes you back to the view with ALL of your photos? Surely if you have thousands of photos on your device and you want to see only photos on a particular date, it would make sense to show only the photos from that date. Even if it generated automatic albums under the album view for each month and year that would be something!

Inhouse distributions apps stopped working after upgrading to version to iOS 18.1.x My issue all is inhouse distributions apps, when I open the application it will force stop. stopped working after upgrading to version 18.1.1. This has happened on multiple iPhones. Some users able use the application on same OS version but application is not working on newly downloaded device. iPhone, then updated to version 18.1.1, they app would not work. We deleted the app and the Enterprise App trust was gone. Then we installed a new version of the app. The phone did not prompt us to trust the Enterprise app again and the app it would open for a second then close. I believe when the app was deleted the Enterprise App was deleted, it’s not actually deleting certificates, because re-installation is not asking to trust certificate again.

Apologies if this is the wrong place, I'm trying to enroll as a developer with my company. A long time ago I was invited to join, but had let the invitation expire. I'm working with my manager to try and get another email sent out inviting me into the program, but I'm not receiving anything in my inbox. Is there a known bug here? Is there something else that needs to be done to send out a second invite?

Unable to search contacts , app crashes Call screen goes compl transparent

I tried to update to the currently released beta version of iPad OS26, but I can't seem to update due to lack of storage space on my iPad. Is there any other way to update besides freeing up space? Model: iPad 8 Storage: 18GB/32GB I would appreciate it if anyone has any information on how to free up storage space in order to update to iPad OS26.

Hello developers! I built a basic trivia app for NCAA Wrestling - I do NOT own an iPad 13. I can't get passed the screenshot for approval Hoping for a person willing to help a newbie out - I'm struggling thanks! Adrian Stewart

Installation has completed login is successful but after 30 secs it returns to login screen safe mode does the same. tried recovery mode and reinstalled. Still in the login loop. what are my choices now?

My iPhone 11 has iOS 18.4 Beta and my new iPhone 16e isn’t supported for iOS 18.4 Beta (for now) and is on iOS 18.3.1 Beta. If anyone knows when it’ll be supported please let me know.

Over the past few months, I’ve been experiencing persistent, abnormal behavior on my iPhone. Here's a short timeline: March 2025: Most apps log me out every time I close them. April 2025: Stored passwords suddenly begin failing across apps and websites. May–June 2025: Password recovery emails from Gmail accounts no longer arrive — suggesting that Gmail itself may be compromised or blocked/intercepted. Given the escalation, I ran several diagnostics and extracted system-level logs. Below is a structured summary of findings that point toward potential remote access, network traffic rerouting, and possibly hidden use of Bluetooth or debugging interfaces. Device Information Model: iPhone17,1 (A17 chip) iOS Version: 18.5 (Build 22F76) Status: Stock, not jailbroken or running a developer build Region: Netherlands Carrier: KPN NL Language/Locale: Dutch (nl-NL) 1. Evidence of Remote Services and XPC Connectivity Source: remotectl_dumpstate.txt More than 50 remote lockdown and diagnostic services are listed as active. Notable entries: com.apple.mobile.lockdown.remote.trusted and .untrusted com.apple.mobile.file_relay.shim.remote com.apple.webinspector.shim.remote com.apple.pcapd.shim.remote com.apple.bluetooth.BTPacketLogger.shim.remote com.apple.mobile.insecure_notification_proxy.remote This volume of .shim.remote and diagnostic services appears highly irregular for a non-debug, non-jailbroken device. 2. Skywalk Network Flows and Unusual Routing Source: skywalk.txt Dozens of flowswitch entries across interfaces like: ipsec0-7, pdp_ip0-2, en0-2, awdl0 Apps such as Gmail, ChatGPT, Preferences, and com.apple.WebKit are marked as defunct, yet persist in flow tables. Two specific daemons — replicatord and siriactionsd — appear on nearly every interface, in both QUIC and TCP6 traffic. skywalkctl flow-route shows multiple external IP paths, with flows routed through ipsec7, owned by kernel_task.0 — indicate tunnelling? 3. System Anomalies and Resource Behavior Inaccessible System Network Tools Source: get-network-info.txt All scutil calls fail (/usr/sbin/scutil does not exist). This blocks access to: DNS configuration (scutil --dns) Proxy and VPN status (scutil --proxy, --nc list) Reachability checks (scutil -r www.apple.com) The absence of scutil is not expected right? Unusual Resource Usage Source: assetsd.diskwrites_resource-2025-06-25.json assetsd, working on behalf of cloudphotod, wrote over 1 GB of memory-backed files in under 1.5 hours. 4. Metadata Confirmation Source: Analytics-2025-06-27-020008.json Confirms: iPhone capacity: 256 GB DRAM: 7.5 GB Carrier: KPN NL Apps marked as highly active ("Games", "Creativity") in analytics also appear as defunct in skywalk, suggesting ghost background processes. Key Questions for the Developer Community Are >50 remote .shim.remote services typical on iOS 18.5 (release build)? Or does this suggest tampering, an MDM configuration, or debug provisioning? Could a misconfigured VPN or MDM profile enable persistent flow-switching across multiple interfaces (e.g., ipsec, pdp, awdl) and reroute app traffic such as Gmail? Is it possible for a test or developer certificate to silently side-load a background daemon, or trigger services like pcapd or file_relay, without showing in Profiles or Settings? Has anyone else seen the scutil binary missing or inaccessible on a stock iPhone? Could this be a sign of intentional lockdown or system modification? If anyone on iOS 18.5 / iPhone17,1 can share their remotectl_dumpstate output, I'd like to compare the service count and see if this behavior is reproducible. I’d appreciate any insight from those familiar with Apple’s system daemons, skywalk internals, or network service behavior. Happy to share sanitized logs or run additional diagnostics if needed. Thanks in advance. get-network-info.txt route-info.txt remotectl_dumpstate.txt [ assetsd.diskwrites_resource-2025-06-25-221428.json

I've got the initial WWDC beta of macOS 26 (25A5279m) installed inside a virtual machine (UTM), but can't seem to update to the second beta. Nothing is showing up within Software Update. Is this because it's within a VM, or am I doing something wrong? It'd be a real pain to have to install a new VM afresh with the RestoreImage for every update.

Hi team, I am trying to enroll my company, in the Apple Developer Program - I am repeatedly receiving a rejection from Apple’s system. It shows in review and when I continue to enrollment, nothing happens. It submits as a new request. I have: ✅ Verified my business name and address with D&B (matches exactly). ✅ Checked that my business is a legal entity (LLP). ✅ Ensured all details match across D&B, UPIK, and Apple’s lookup tool. ✅ Attempted re-submission multiple times without success. However, despite these steps, I am still unable to proceed. Please help.

I’ve encountered a critical issue in macOS Tahoe (Beta) that affects the Photos app or any app that leverages Apple’s editing frameworks. After editing certain photos—whether applying filters, cropping, or making basic adjustments—the image suddenly turns completely black upon saving or exiting the edit mode. Details: macOS Version: macOS Tahoe (latest beta) Affected App(s): Photos, Preview, and some third-party editing apps Steps to Reproduce: Open a photo in the Photos app Make any basic edit (e.g., crop, adjust brightness) Click “Done” The edited photo appears entirely black Notes: Happens with both JPEG and HEIC formats Original photo appears fine before editing Exporting the photo also results in a black image Restarting the app/system does not resolve the issue iCloud Photos is enabled This issue seems related to the image rendering pipeline post-editing, possibly tied to Core Image or GPU rendering frameworks. It severely affects photo usability and could result in permanent data loss if backups are not maintained. Please advise if a workaround exists or if this bug has been logged already. Happy to provide system logs or sample images if needed.

A few days ago I installed beta 1 of macOS 26 Tahoe on a spare MacBook Pro 14-inch M4. Everything went well, and it looks okay (well, I don't like it at all, but hey-ho), and I shut it down. I started it up today, and it rejects my login password every time, then locks my account. When I click the link to "Restart and show password reset options" I'm asked for my Apple ID details, so I enter the correct email and password, then the MBP reboots and I'm back on the login screen with no indication that anything has changed. Guess I'm stuck now... FB18364657

Updated iPhone to 26 beta 2, everything is ok but battery, battery is changed, not original. My phone can't charge higher than 1% and turns off every 5 minutes, even connecting to wireless charger and cable at the same time don't work, restored iPhone thru iTunes.I hope I will be able to install new beta without any problems because loving the new design, hoping for the best. Thanks. My FB-FB18327769

We’re integrating Sign in with Apple using Apple’s official JavaScript SDK: https://appleid.cdn-apple.com/appleauth/static/jsapi/appleid/1/en_US/appleid.auth.js We’ve successfully used this setup with an older Service ID, but when we try to use any newly created Service ID, we get the following error immediately when calling AppleID.auth.signIn(): invalid_client This happens before any request reaches our backend. The same flow, redirect URI, and frontend code works fine with an old Service ID — but fails with new ones. ✅ What We’ve Verified: The Service ID (e.g., com.projectx.web.login) is created under Apple Developer → Identifiers → Service IDs The redirect URI is correct and matches exactly (HTTPS, no trailing slash) No client_secret is passed in the frontend (by design) We’re using usePopup: true ❌ What Doesn’t Work: Any new Service ID we create — even on the same domain and configuration — fails with invalid_client. 🔁 What We’ve Tried: Creating multiple new Service IDs Waiting 48+ hours in case of propagation delays Validating HTTPS and redirect URI setup Comparing all settings with the working (older) Service ID (which we deleted since we thought that was causing a problem) Testing in different environments and browsers ❓ Questions: Why do newly created Service IDs fail with invalid_client while older ones work? Are there undocumented requirements, propagation delays, or steps for new Service IDs to become active? Is this a known limitation or bug in the SDK? 💻 Our Code: import { useEffect } from "react"; import { Button, Box } from "@mui/material"; import api from "../utils/api"; // Axios wrapper import AppleIcon from "@mui/icons-material/Apple"; import MainAuthStyles from "../pages/MainAuthStyles"; import { useUser } from "../../../user-module/src/contexts/UserContext"; import { useNavigate } from "react-router-dom"; // Apple global type declare global { interface Window { AppleID: any; } } type AppleSignInButtonProps = { setApiError: (msg: string) => void; }; const AppleLogInButton = ({ setApiError }: AppleSignInButtonProps) => { const { user, setUser } = useUser(); const navigate = useNavigate(); useEffect(() => { if (!window.AppleID) return; window.AppleID.auth.init({ clientId: import.meta.env.VITE_APPLE_CLIENT_ID, scope: "name email", redirectURI: import.meta.env.VITE_APPLE_REDIRECT_URI, usePopup: true, }); }, []); const handleAppleLogin = async () => { try { const response = await window.AppleID.auth.signIn(); const { id_token, code, user } = response.authorization; const res = await api.post("/auth/apple-login", { idToken: id_token, code, user, rememberMe: true, }); if (res.data.success == true && res.data.user.userDataInitialised == true ) { setUser({ id: res.data.user.id ? res.data.user.id : '', fullName: res.data.user.fullName ? res.data.user.fullName : '', email: res.data.user.email ? res.data.user.email : '', role: res.data.user.role ? res.data.user.role : '', signUpType: res.data.user.signUpType ? res.data.user.signUpType : '', userDataInitialised: res.data.user.userDataInitialised ? res.data.user.userDataInitialised : false, }); localStorage.setItem("accessToken", res.data.accessToken); localStorage.setItem("refreshToken", res.data.refreshToken); navigate("/app") } else { setApiError("Unrecognized login method") return; } } catch (err) { console.error("Apple Sign-In failed", err); setApiError("AppleSignInFailed"); } }; return ( <Box mt={2}> <Button variant="outlined" fullWidth onClick={handleAppleLogin} className="AuthAppleButton" startIcon={<AppleIcon />} > Log in with Apple </Button> </Box> ); }; export default AppleLogInButton; Any help from the Apple team or anyone who's resolved this issue would be appreciated — we’re currently blocked on deploying new environments due to this error. Thanks!