JavaScript

RSS for tag

Discuss the JavaScript programing language.

Posts under JavaScript tag

200 Posts

Post

Replies

Boosts

Views

Activity

MusicKitJS | Cannot play explicit songs | CONTENT_RESTRICTED
[Ticket on Feedback Assistant FB12353357] Hi there, We’re experiencing issues playing explicit songs using MusicKitJS for the Web (tested on both stable v1 and beta v3). Upon calling the SDK’s “play()” function, the following error gets logged in the console “CONTENT_RESTRICTED: Content restricted” and playback doesn’t begin. The Storefront we’ve tested in is “it”, but very likely all of them are impacted with the issue, here’s a few Adam IDs of affected tracks: 1681182396, 1683117248, 1669607876. A quick check with the REST APIs reveals indeed that the relevant thing all 3 of them have in common is "contentRating" being "explicit”. The bug isn’t however easy or predictable to replicate because it seems that it can be somewhat solved by fiddling with both the “Screen Time” restrictions settings within an iOS/iPadOS device (of course logged in with the same Apple account), as well as with the “Parental Controls” dashboard located in the Web version of the Apple Music’s settings page. We’re still not 100% sure what exactly “triggers” the fix, but both mentioned dashboards above are essential in attempting to solve it by trial and error. Specifically: in the “Parental Controls” dashboard what helps is actually turning ON the restrictions with the toggle, and then easing them up the most by specifically setting the less restricted available option in all 3 dropdown menus (pretty baffling); in the “Screen time” dashboard what helps is simply enabling/disabling the feature itself altogether, as well as the “Content & Privacy restrictions” toggle, and changing the level of allowed content between “Clean” and “Explicit”; I also want to highlight the fact that during the entire process, for the issue to be actually solved, users every time had to to restart their iPhone/iPad multiple times after changing a setting in “Screen time”, along with deauthorizing/authorizing (logging out and back in) their Apple Music account from the MusicKitJS SDK. The issue seems to always affect freshly created Apple accounts right from the start, we’re not aware of methods that can lead to the bug “coming back” and starting to happen again after being solved manually with the process above (meddling “randomly” with dashboards). It’s a pretty serious one because many of our users do not posses an Apple device and only use their Apple Music subscription on the Web and/or their Android device, meaning that the “Screen time” dashboard isn’t available for them. We’ve never been able to solve the problem on an Apple ID account solely by fiddling with the “Parental Controls” dashboard located in the Web version of the Apple Music’s settings page: tinkering with the “Screen time” settings was essential every single time, meaning owning an Apple device is essential to solve it. Last thing I’m adding is that the issue doesn’t seem to also affect listening to these explicit songs directly with the various first-party Apple Music clients (tested on the iOS native app, Android native app, and on the Apple Music WebApp). Steps to reproduce: on the Web, create a new Apple ID account and activate an Apple Music subscription (do not login with said account on an Apple device); go to the Apple Music WebApp settings page at music.apple.com/account/settings and make sure that the “Parental Controls” restrictions are turned OFF; open any explicit song in the Apple Music WebApp and confirm that playback is allowed; login and authorize the newly created account using any website/application integrated with the MusicKitJS SDK (v1 or v3, doesn’t matter); open the same explicit song as before (or any other) in said third-party client that uses the SDK and verify that playback doesn’t begin and an error “CONTENT_RESTRICTED: Content restricted” is logged in the console upon playing. Additional infos: Apple ID account region and language: Italy - Italian; Storefront affected: IT but possibly all of them; MusicKitJS versions affected: both v1 and v3; Browser where the issue was reproduced: Chrome v114. Attached you’ll find some informational screenshots. Thanks!
3
0
2k
2d
Apple Calculator
Hello. I'm using Sololearn and ChatGPT to learn how to code. I've made a calculator before, but I want to make one similar to the one on iPhone. Is ok to have a link to apple.com or do I say I was inspired by Apple Here is the code I currently have: HTML <!DOCTYPE html><html> <head> <title>Page Title</title> <meta name="viewport" content="width=device-width, initial-scale=1"> </head> <body> <div class="calculator"> <input class="display" type="text"> <div class = "scientific"> <button>(</button> <button>)</button> <button>mc</button> <button>m+</button> <button>m-</button> <button>mr</button> </div> <div class ="standard"> <button class="utility" id="backspace">&#9003;</button> <button class="utility" id="clear">AC</button> <button class="utility" id="percent">%</button> <button class="operator">/</button> <button class="number digit">7</button> <button class="number digit">8</button> <button class="number digit">9</button> <button class="operator">*</button> <button class="number digit">4</button> <button class="number digit">5</button> <button class="number digit">6</button> <button class="operator">-</button> <button class="number digit">1</button> <button class="number digit">2</button> <button class="number digit">3</button> <button class="operator">+</button> <button class="number" id="plusmn"><sup>+</sup>&frasl;<sub>-</sub></button> <button class="number digit">0</button> <button class="number" id="decimal">.</button> <button class="utility equals" id="equals">=</button> </div> </div> </body></html> ``` ``` CSSbody{ background-color: black; } html, body { margin: 0; width: 100%; height: 100%; background-color: black; } input { font-size: 48px; box-sizing: border-box; width: 100%;} .utility { background-color: #666; color: white; } .operator { background-color: orange; color: white; } .equals{ background-color: orange; color: white; } .number{ background-color: #333; color: white; } .calculator { display: grid; /*grid-template-columns: repeat(4, 1fr);*/ grid-template-columns: 1fr; gap: 4px; width: 100%; box-sizing: border-box; padding: 12px; position: fixed; bottom: 0; left: 0;} .calculator button { width: 100%; aspect-ratio: 1; border: none; border-radius: 50%; font-size: 32px; } .scientific{ display: grid; grid-template-columns: repeat(6, 1fr); gap: 4px;} .standard{ display: grid; grid-template-columns: repeat(4, 1fr); gap: 4px;} .display { color: white; background-color: black; border: none; height: 100px; font-size: 48px; text-align: right; box-sizing: border-box; width: 100%; } /* .display { grid-column: 1 / -1; color: white; background-color: black; border: none; height: 100px; font-size: 48px; text-align: right; box-sizing: border-box; width: 100%; } */ /* .zero { grid-column: span 2; border-radius: 40px; aspect-ratio: auto;} .calculator button.zero { aspect-ratio: auto; border-radius: 40px;} */ JS const display = document.querySelector(".display"); let fontSize = 48; function adjustFontSize() { fontSize = 48 - display.value.length * .99; if (fontSize < 20) { fontSize = 20; } display.style.fontSize = fontSize + "px"; } const buttonsJS = document.querySelectorAll(".digit"); buttonsJS.forEach(function(buttonJS) { buttonJS.addEventListener("click", function() { display.value += buttonJS.textContent; adjustFontSize(); }); }); const clear = document.querySelector("#clear"); clear.addEventListener("click", function() { display.value = ""; adjustFontSize(); }); const backspace = document.querySelector("#backspace"); backspace.addEventListener("click", function() { display.value = display.value.slice (0, -1); adjustFontSize(); }); const percent = document.querySelector("#percent"); percent.addEventListener("click", function(){ display.value /= 100; adjustFontSize(); }); const plusmn = document.querySelector("#plusmn"); plusmn.addEventListener("click", function(){ display.value /= -1; adjustFontSize(); }); const decimal = document.querySelector("#decimal"); decimal.addEventListener("click", function(){ if (!display.value.includes(".")) { display.value += "."; // Add the decimal point here } adjustFontSize();}); const operators = document.querySelectorAll(".operator"); operators.forEach(function(operator) { operator.addEventListener("click", function() { display.value += operator.textContent; adjustFontSize(); }); }); const equals = document.querySelector("#equals"); equals.addEventListener("click", function() { display.value = eval(display.value); adjustFontSize(); }); /* const display = document.querySelector(".display"); const buttonJS = document.querySelector(".digit"); buttonJS.addEventListener("click", function() { console.log("You clicked the button!"); }); const buttonsJS = document.querySelectorAll(".digit"); buttonsJS.forEach(function(buttonJS) { buttonJS.addEventListener("click", function() { display.value += buttonJS.textContent; }); }); */
1
0
842
2w
iOS/iPadOS 18+: Camera Video Recorded via Browser Appears Flipped or Upside Down
I'm encountering an issue with front camera video recordings via browser (Safari/Chrome) on devices running iOS/iPadOS 18 and above: On iPad, the recorded video appears upside down. On iPhone, the recorded video is rotated 90 degrees. The rear camera functions correctly without orientation issues. This problem seems specific to browser-based recordings, as the native Camera app records videos with the correct orientation. Has anyone else experienced this behavior? Is there a known workaround or fix? The preview while recording is fine, the recorded video is oriented incorrectly.
2
1
1.8k
Sep ’26
TestFlight iOS app crashes immediately on launch, but build uploads successfully
Our iOS app uploads successfully to App Store Connect and appears in TestFlight, but it crashes immediately on launch. App name: Axioma Pay Bundle ID: uk.co.axiomapay.app Distribution: TestFlight Framework: Expo / React Native Device tested: iPad via TestFlight The app installs, the icon appears, but tapping Open causes an immediate crash. One earlier build displayed this runtime message: Cannot read property 'ErrorBoundary' of undefined Crash logs show the app aborting on the React Native ExceptionsManagerQueue with SIGABRT / EXC_CRASH. We do not currently have a focused minimal Xcode sample project because this is an Expo/EAS React Native production build. We can provide .ips crash logs and App Store Connect/TestFlight build details. Can Apple help confirm whether this crash appears to be caused by: App Store/TestFlight processing, provisioning/signing/entitlements, an iOS runtime issue, or an app-side React Native JavaScript startup exception? Latest TestFlight build crashes immediately after launch.
1
0
1.1k
Aug ’26
MacOS shortcut for running Javascript on a Safari page fails
I'm trying to run a MacOS shortcut using the "Run JavaScript on Active Safari Tab" action. I consistently get the error "Make sure that 'Allow JavaScript from Apple Events' is enabled in the Develop menu in Safari." The Develop menu in Safari does not contain this switch (in Tahoe 26.5.1), but if you go to Developer Settings... a dialog opens that includes the required switch. I've ensured that the switch is set on, but I continue to get the runtime error in the shortcut JavaScript. What am I missing?
1
0
1.6k
Jul ’26
JavaScript/Swift Interoperability
I think that it would be helpful to have better interoperability between Swift and JavaScript. There are a lot of useful packages on NPM that don't have equivalents for Swift. It would be helpful if Apple provided easier ways to use NPM packages in a Swift project. Currently, the JavaScriptCore framework is missing many standard things used in many packages, like the fetch API. It would be helpful to be able to run sandboxed JavaScript code inside of a Swift app but allow access to specific domains, folders, etc., using a permissions system similar to Deno.
6
1
4.6k
Jan ’26
I have a question about Safari running in the background on iOS and iPadOS.
I coded two demo websites as follows (both written in NextJS): Website 1: I coded an interval counter that increments every 1 second. Website 2: I used the MediaRecorder API (described in the WebKit documentation: https://webkit.org/blog/11353/mediarecorder-api/). In the ondataavailable function, I periodically send a blob (once every 1 second) to my server. In the backend, I coded a POST API to upload this blob. I noticed that with website 1, the interval doesn't work when I run Safari in the background, even on iOS and iPadOS. However, website 2 works, meaning it still calls my API normally (I tried running Safari in the background for about 1-2 hours and it worked). So, does this mean Apple allows native APIs like MediaRecorder and its callbacks to run in the background?
0
0
1.4k
Dec ’25
Detecting Navigation Redirect Chains
I'm building a macOS extension that needs to track multi-step navigation chains (A → B → C) to adjust behavior based on where users came from. Current approach: Using webNavigation.onBeforeNavigate to detect intermediate steps, but experiencing issues in Safari that don't occur on Chrome/Firefox/Edge. Questions: Is webNavigation the right API for tracking redirect chains in Safari? Does ITP/Private Browsing affect event delivery? Any alternative approaches recommended? (Safari version 26.0.1) Any guidance appreciated!
3
0
2.0k
Dec ’25
DOMContentLoaded not working in Safari App Extension
I am trying to run JavaScript only after the page has loaded, and according to here - https://developer.apple.com/documentation/safariservices/safari_app_extensions/injecting_a_script_into_a_webpage, I should use DOMContentLoaded. However, it does not seem to work. This is my content.js file: function runOnStart() {     document.addEventListener('DOMContentLoaded', function(e) {         document.body.style.background = "rgb(20, 20, 20)";         document.html.style.background = "rgb(20, 20, 20)";                var divElements = document.body.getElementsByTagName('div');         for(var i = 0; i < divElements.length; i++) {             let elem = divElements[i];             elem.style.background = "rgba(255, 255, 255, 0.05)";         }     }); } runOnStart(); If I take the code outside of the event listener, it runs fine, but a lot of the elements haven't loaded in yet so it doesn't work as it should. The function is definitely running, but the event listener simply doesn't work. I appreciate any help you can give!
12
3
12k
Dec ’25
iOS App Store Tester Facing Network Timeouts since iOS 26?
Our iOS/iPad app is built with React Native. We use Axios as our HTTP client. Our app has been out on the app store for 2+ years and we've never had issues with reviews. Since iOS 26 came out, our app has been constantly getting rejected because the Apple tester keeps facing network timeout issues when our app makes requests to our API services. Our API stack is already configured to support IPv6 networks, and our regular user base does not run into the issues the Apple tester is seeing. None of our developers nor our internal testers have been able to reproduce the issue the Apple tester is facing. We've tried a number of things to debug the potential issue: Added a ping check on app startup. We used the native fetch present in React Native apps as well as our Axios client (with the default XHR/HTTP adapter). None of the pings make it to our API services. Added higher timeouts on app startup to let the Apple tester have more time to reach our services while their simulator device is able to connect. We've read that the environment that Apple testers use can sometimes take longer to establish an initial connection, even though packages like NetInfo from React Native report that they are connected to WiFi as soon as the app starts. Switched our Axios client adapter to use the native fetch. We did this since we noticed that Mixpanel, our tracking library, uses the native fetch in their React Native SDK and we've confirmed that requests on their end do make it through when the Apple tester is testing our app. We're running out of ideas since the issue is pretty obscure and we haven't been able to reproduce it yet, not even by following the Apple guide to set up a local IPv6 NAT64 network to be as close to their environment as possible. We've also tried testing the app while connected to VPNs from different locations to no avail. Like I said before, we noticed that this issues started for the Apple tester with the release of iOS 26, so we're wondering if there are known issues in the community that might relate to what we're experiencing. The most recent finding we've made is that some other developers report new issues with HTTP 3/QUIC on iOS. We've seen recommendations about turning off explicit support for HTTP 3 on our services, which seems to have helped other developers.
0
4
729
Nov ’25
Twilio Voice iOS SDK: callInvite is missing when accepting incoming call from CallKit or React Native
I'm integrating Twilio Voice (v6.12.1) into my React Native app (using Swift bridging for iOS) and have implemented full VoIP, PushKit, and CallKit support for incoming calls. ✅ What works: Incoming calls trigger the VoIP push and display the full-screen CallKit interface (or fallback UI). Decline Call works as expected. Call logs and events print correctly. ❌ Problem: When I try to accept the call using the CallKit Accept button or React Native fallback UI, I consistently get: ❌ [TwilioVoiceModule] answerCall() callInvite is missing. I also noticed that the console logs for answerCall() are being printed three times in a row, even though the accept button is only pressed once. Additionally in the first time console, answerCall() CallInvite found, accepting... 🔍 Observations: The callInvite is properly received when the VoIP push arrives. But when answerCall() is triggered, callInvite becomes nil. This happens in CallKit accept, RN UI accept, and even notification banner accept. 📦 How it's set up (summarized): PushKit Registration – via PKPushRegistry in AppDelegate.swift VoIP push handling – forwards payload to TwilioVoiceModule.handleIncomingPush() CallKit integration – uses CXProviderDelegate to report and handle accept actions JS Bridge – emits acceptCallAction to JS React Native calls TwilioVoiceModule.answerCall(uuid, callSid) In answerCall() method: self.callInvite is nil – so call cannot be accepted. Attaching the link to view the relevant code: https://docs.google.com/document/d/15pNjKrfk954OaotpMIEh3xQUtst---1K45DBXoYctGM/edit?usp=sharing 💡 Call Accept Flow (iOS): VoIP Push → TwilioVoiceModule.handleIncomingPush() Twilio SDK creates callInvite reportNewIncomingCall() triggers CallKit UI On accept: CXAnswerCallAction → emits event to JS RN calls TwilioVoiceModule.answerCall(uuid, callSid) Problem: callInvite is already nil ❓ What I'm trying to understand: Why is callInvite becoming nil before answerCall() is called? Why are the logs showing the answerCall() call 3 times? Is there a race condition or multiple accept triggers? Should I ensure callInvite is accepted only once across all 3 accept paths? ** 💬 Any help would be appreciated.** 📱 Environment: React Native 0.78.x iOS 17+ Swift bridging with TwilioVoiceModule.swift Twilio Voice SDK 6.12.1 PushKit + CallKit + react-native-callkeep
1
0
1.3k
Aug ’25
PAC ( Automatic Proxy Configuration ) Script Not working with Safari MacOS version 15.1
We have written a PAC script that blocklists certain domains and whitelists others. We went to Settings > Network > Wi-Fi (the network we are using), then clicked on Details, and under Proxies, we added the PAC file URL in the Automatic Proxy Configuration section. We tried hosting the PAC file both on localhost and on a separate HTTP server. After saving the settings, we tested several URLs. The blocking and allowing behavior works correctly in all browsers except Safari. Below is the PAC script we are using for your reference. The script works as expected in browsers other than Safari. This is how the PAC script URL looks: http://localhost:31290/proxy.pac function FindProxyForURL(url, host) { var blacklist = new Set(["facebook.com", "deepseek.com"]); var b_list = [...blacklist]; for (let i = 0; i < b_list.length; i++) { let ele = b_list[i] + "*"; if (shExpMatch(host, ele) || shExpMatch(url, ele)) { return "PROXY localhost:8086"; } } if (isIPBlocked(whitelist_subnet, hostIP)) { return "PROXY localhost:8087"; } if (isIPBlocked(blacklist_subnet, hostIP)) { return "PROXY localhost:8086"; } return "PROXY localhost:8080"; }
2
0
1.2k
Jul ’25
MusicKitJS | Cannot play explicit songs | CONTENT_RESTRICTED
[Ticket on Feedback Assistant FB12353357] Hi there, We’re experiencing issues playing explicit songs using MusicKitJS for the Web (tested on both stable v1 and beta v3). Upon calling the SDK’s “play()” function, the following error gets logged in the console “CONTENT_RESTRICTED: Content restricted” and playback doesn’t begin. The Storefront we’ve tested in is “it”, but very likely all of them are impacted with the issue, here’s a few Adam IDs of affected tracks: 1681182396, 1683117248, 1669607876. A quick check with the REST APIs reveals indeed that the relevant thing all 3 of them have in common is "contentRating" being "explicit”. The bug isn’t however easy or predictable to replicate because it seems that it can be somewhat solved by fiddling with both the “Screen Time” restrictions settings within an iOS/iPadOS device (of course logged in with the same Apple account), as well as with the “Parental Controls” dashboard located in the Web version of the Apple Music’s settings page. We’re still not 100% sure what exactly “triggers” the fix, but both mentioned dashboards above are essential in attempting to solve it by trial and error. Specifically: in the “Parental Controls” dashboard what helps is actually turning ON the restrictions with the toggle, and then easing them up the most by specifically setting the less restricted available option in all 3 dropdown menus (pretty baffling); in the “Screen time” dashboard what helps is simply enabling/disabling the feature itself altogether, as well as the “Content & Privacy restrictions” toggle, and changing the level of allowed content between “Clean” and “Explicit”; I also want to highlight the fact that during the entire process, for the issue to be actually solved, users every time had to to restart their iPhone/iPad multiple times after changing a setting in “Screen time”, along with deauthorizing/authorizing (logging out and back in) their Apple Music account from the MusicKitJS SDK. The issue seems to always affect freshly created Apple accounts right from the start, we’re not aware of methods that can lead to the bug “coming back” and starting to happen again after being solved manually with the process above (meddling “randomly” with dashboards). It’s a pretty serious one because many of our users do not posses an Apple device and only use their Apple Music subscription on the Web and/or their Android device, meaning that the “Screen time” dashboard isn’t available for them. We’ve never been able to solve the problem on an Apple ID account solely by fiddling with the “Parental Controls” dashboard located in the Web version of the Apple Music’s settings page: tinkering with the “Screen time” settings was essential every single time, meaning owning an Apple device is essential to solve it. Last thing I’m adding is that the issue doesn’t seem to also affect listening to these explicit songs directly with the various first-party Apple Music clients (tested on the iOS native app, Android native app, and on the Apple Music WebApp). Steps to reproduce: on the Web, create a new Apple ID account and activate an Apple Music subscription (do not login with said account on an Apple device); go to the Apple Music WebApp settings page at music.apple.com/account/settings and make sure that the “Parental Controls” restrictions are turned OFF; open any explicit song in the Apple Music WebApp and confirm that playback is allowed; login and authorize the newly created account using any website/application integrated with the MusicKitJS SDK (v1 or v3, doesn’t matter); open the same explicit song as before (or any other) in said third-party client that uses the SDK and verify that playback doesn’t begin and an error “CONTENT_RESTRICTED: Content restricted” is logged in the console upon playing. Additional infos: Apple ID account region and language: Italy - Italian; Storefront affected: IT but possibly all of them; MusicKitJS versions affected: both v1 and v3; Browser where the issue was reproduced: Chrome v114. Attached you’ll find some informational screenshots. Thanks!
Replies
3
Boosts
0
Views
2k
Activity
2d
Apple Calculator
Hello. I'm using Sololearn and ChatGPT to learn how to code. I've made a calculator before, but I want to make one similar to the one on iPhone. Is ok to have a link to apple.com or do I say I was inspired by Apple Here is the code I currently have: HTML <!DOCTYPE html><html> <head> <title>Page Title</title> <meta name="viewport" content="width=device-width, initial-scale=1"> </head> <body> <div class="calculator"> <input class="display" type="text"> <div class = "scientific"> <button>(</button> <button>)</button> <button>mc</button> <button>m+</button> <button>m-</button> <button>mr</button> </div> <div class ="standard"> <button class="utility" id="backspace">&#9003;</button> <button class="utility" id="clear">AC</button> <button class="utility" id="percent">%</button> <button class="operator">/</button> <button class="number digit">7</button> <button class="number digit">8</button> <button class="number digit">9</button> <button class="operator">*</button> <button class="number digit">4</button> <button class="number digit">5</button> <button class="number digit">6</button> <button class="operator">-</button> <button class="number digit">1</button> <button class="number digit">2</button> <button class="number digit">3</button> <button class="operator">+</button> <button class="number" id="plusmn"><sup>+</sup>&frasl;<sub>-</sub></button> <button class="number digit">0</button> <button class="number" id="decimal">.</button> <button class="utility equals" id="equals">=</button> </div> </div> </body></html> ``` ``` CSSbody{ background-color: black; } html, body { margin: 0; width: 100%; height: 100%; background-color: black; } input { font-size: 48px; box-sizing: border-box; width: 100%;} .utility { background-color: #666; color: white; } .operator { background-color: orange; color: white; } .equals{ background-color: orange; color: white; } .number{ background-color: #333; color: white; } .calculator { display: grid; /*grid-template-columns: repeat(4, 1fr);*/ grid-template-columns: 1fr; gap: 4px; width: 100%; box-sizing: border-box; padding: 12px; position: fixed; bottom: 0; left: 0;} .calculator button { width: 100%; aspect-ratio: 1; border: none; border-radius: 50%; font-size: 32px; } .scientific{ display: grid; grid-template-columns: repeat(6, 1fr); gap: 4px;} .standard{ display: grid; grid-template-columns: repeat(4, 1fr); gap: 4px;} .display { color: white; background-color: black; border: none; height: 100px; font-size: 48px; text-align: right; box-sizing: border-box; width: 100%; } /* .display { grid-column: 1 / -1; color: white; background-color: black; border: none; height: 100px; font-size: 48px; text-align: right; box-sizing: border-box; width: 100%; } */ /* .zero { grid-column: span 2; border-radius: 40px; aspect-ratio: auto;} .calculator button.zero { aspect-ratio: auto; border-radius: 40px;} */ JS const display = document.querySelector(".display"); let fontSize = 48; function adjustFontSize() { fontSize = 48 - display.value.length * .99; if (fontSize < 20) { fontSize = 20; } display.style.fontSize = fontSize + "px"; } const buttonsJS = document.querySelectorAll(".digit"); buttonsJS.forEach(function(buttonJS) { buttonJS.addEventListener("click", function() { display.value += buttonJS.textContent; adjustFontSize(); }); }); const clear = document.querySelector("#clear"); clear.addEventListener("click", function() { display.value = ""; adjustFontSize(); }); const backspace = document.querySelector("#backspace"); backspace.addEventListener("click", function() { display.value = display.value.slice (0, -1); adjustFontSize(); }); const percent = document.querySelector("#percent"); percent.addEventListener("click", function(){ display.value /= 100; adjustFontSize(); }); const plusmn = document.querySelector("#plusmn"); plusmn.addEventListener("click", function(){ display.value /= -1; adjustFontSize(); }); const decimal = document.querySelector("#decimal"); decimal.addEventListener("click", function(){ if (!display.value.includes(".")) { display.value += "."; // Add the decimal point here } adjustFontSize();}); const operators = document.querySelectorAll(".operator"); operators.forEach(function(operator) { operator.addEventListener("click", function() { display.value += operator.textContent; adjustFontSize(); }); }); const equals = document.querySelector("#equals"); equals.addEventListener("click", function() { display.value = eval(display.value); adjustFontSize(); }); /* const display = document.querySelector(".display"); const buttonJS = document.querySelector(".digit"); buttonJS.addEventListener("click", function() { console.log("You clicked the button!"); }); const buttonsJS = document.querySelectorAll(".digit"); buttonsJS.forEach(function(buttonJS) { buttonJS.addEventListener("click", function() { display.value += buttonJS.textContent; }); }); */
Replies
1
Boosts
0
Views
842
Activity
2w
iOS/iPadOS 18+: Camera Video Recorded via Browser Appears Flipped or Upside Down
I'm encountering an issue with front camera video recordings via browser (Safari/Chrome) on devices running iOS/iPadOS 18 and above: On iPad, the recorded video appears upside down. On iPhone, the recorded video is rotated 90 degrees. The rear camera functions correctly without orientation issues. This problem seems specific to browser-based recordings, as the native Camera app records videos with the correct orientation. Has anyone else experienced this behavior? Is there a known workaround or fix? The preview while recording is fine, the recorded video is oriented incorrectly.
Replies
2
Boosts
1
Views
1.8k
Activity
Sep ’26
TestFlight iOS app crashes immediately on launch, but build uploads successfully
Our iOS app uploads successfully to App Store Connect and appears in TestFlight, but it crashes immediately on launch. App name: Axioma Pay Bundle ID: uk.co.axiomapay.app Distribution: TestFlight Framework: Expo / React Native Device tested: iPad via TestFlight The app installs, the icon appears, but tapping Open causes an immediate crash. One earlier build displayed this runtime message: Cannot read property 'ErrorBoundary' of undefined Crash logs show the app aborting on the React Native ExceptionsManagerQueue with SIGABRT / EXC_CRASH. We do not currently have a focused minimal Xcode sample project because this is an Expo/EAS React Native production build. We can provide .ips crash logs and App Store Connect/TestFlight build details. Can Apple help confirm whether this crash appears to be caused by: App Store/TestFlight processing, provisioning/signing/entitlements, an iOS runtime issue, or an app-side React Native JavaScript startup exception? Latest TestFlight build crashes immediately after launch.
Replies
1
Boosts
0
Views
1.1k
Activity
Aug ’26
MacOS shortcut for running Javascript on a Safari page fails
I'm trying to run a MacOS shortcut using the "Run JavaScript on Active Safari Tab" action. I consistently get the error "Make sure that 'Allow JavaScript from Apple Events' is enabled in the Develop menu in Safari." The Develop menu in Safari does not contain this switch (in Tahoe 26.5.1), but if you go to Developer Settings... a dialog opens that includes the required switch. I've ensured that the switch is set on, but I continue to get the runtime error in the shortcut JavaScript. What am I missing?
Replies
1
Boosts
0
Views
1.6k
Activity
Jul ’26
JavaScript/Swift Interoperability
I think that it would be helpful to have better interoperability between Swift and JavaScript. There are a lot of useful packages on NPM that don't have equivalents for Swift. It would be helpful if Apple provided easier ways to use NPM packages in a Swift project. Currently, the JavaScriptCore framework is missing many standard things used in many packages, like the fetch API. It would be helpful to be able to run sandboxed JavaScript code inside of a Swift app but allow access to specific domains, folders, etc., using a permissions system similar to Deno.
Replies
6
Boosts
1
Views
4.6k
Activity
Jan ’26
I have a question about Safari running in the background on iOS and iPadOS.
I coded two demo websites as follows (both written in NextJS): Website 1: I coded an interval counter that increments every 1 second. Website 2: I used the MediaRecorder API (described in the WebKit documentation: https://webkit.org/blog/11353/mediarecorder-api/). In the ondataavailable function, I periodically send a blob (once every 1 second) to my server. In the backend, I coded a POST API to upload this blob. I noticed that with website 1, the interval doesn't work when I run Safari in the background, even on iOS and iPadOS. However, website 2 works, meaning it still calls my API normally (I tried running Safari in the background for about 1-2 hours and it worked). So, does this mean Apple allows native APIs like MediaRecorder and its callbacks to run in the background?
Replies
0
Boosts
0
Views
1.4k
Activity
Dec ’25
Detecting Navigation Redirect Chains
I'm building a macOS extension that needs to track multi-step navigation chains (A → B → C) to adjust behavior based on where users came from. Current approach: Using webNavigation.onBeforeNavigate to detect intermediate steps, but experiencing issues in Safari that don't occur on Chrome/Firefox/Edge. Questions: Is webNavigation the right API for tracking redirect chains in Safari? Does ITP/Private Browsing affect event delivery? Any alternative approaches recommended? (Safari version 26.0.1) Any guidance appreciated!
Replies
3
Boosts
0
Views
2.0k
Activity
Dec ’25
DOMContentLoaded not working in Safari App Extension
I am trying to run JavaScript only after the page has loaded, and according to here - https://developer.apple.com/documentation/safariservices/safari_app_extensions/injecting_a_script_into_a_webpage, I should use DOMContentLoaded. However, it does not seem to work. This is my content.js file: function runOnStart() {     document.addEventListener('DOMContentLoaded', function(e) {         document.body.style.background = "rgb(20, 20, 20)";         document.html.style.background = "rgb(20, 20, 20)";                var divElements = document.body.getElementsByTagName('div');         for(var i = 0; i < divElements.length; i++) {             let elem = divElements[i];             elem.style.background = "rgba(255, 255, 255, 0.05)";         }     }); } runOnStart(); If I take the code outside of the event listener, it runs fine, but a lot of the elements haven't loaded in yet so it doesn't work as it should. The function is definitely running, but the event listener simply doesn't work. I appreciate any help you can give!
Replies
12
Boosts
3
Views
12k
Activity
Dec ’25
iOS App Store Tester Facing Network Timeouts since iOS 26?
Our iOS/iPad app is built with React Native. We use Axios as our HTTP client. Our app has been out on the app store for 2+ years and we've never had issues with reviews. Since iOS 26 came out, our app has been constantly getting rejected because the Apple tester keeps facing network timeout issues when our app makes requests to our API services. Our API stack is already configured to support IPv6 networks, and our regular user base does not run into the issues the Apple tester is seeing. None of our developers nor our internal testers have been able to reproduce the issue the Apple tester is facing. We've tried a number of things to debug the potential issue: Added a ping check on app startup. We used the native fetch present in React Native apps as well as our Axios client (with the default XHR/HTTP adapter). None of the pings make it to our API services. Added higher timeouts on app startup to let the Apple tester have more time to reach our services while their simulator device is able to connect. We've read that the environment that Apple testers use can sometimes take longer to establish an initial connection, even though packages like NetInfo from React Native report that they are connected to WiFi as soon as the app starts. Switched our Axios client adapter to use the native fetch. We did this since we noticed that Mixpanel, our tracking library, uses the native fetch in their React Native SDK and we've confirmed that requests on their end do make it through when the Apple tester is testing our app. We're running out of ideas since the issue is pretty obscure and we haven't been able to reproduce it yet, not even by following the Apple guide to set up a local IPv6 NAT64 network to be as close to their environment as possible. We've also tried testing the app while connected to VPNs from different locations to no avail. Like I said before, we noticed that this issues started for the Apple tester with the release of iOS 26, so we're wondering if there are known issues in the community that might relate to what we're experiencing. The most recent finding we've made is that some other developers report new issues with HTTP 3/QUIC on iOS. We've seen recommendations about turning off explicit support for HTTP 3 on our services, which seems to have helped other developers.
Replies
0
Boosts
4
Views
729
Activity
Nov ’25
Twilio Voice iOS SDK: callInvite is missing when accepting incoming call from CallKit or React Native
I'm integrating Twilio Voice (v6.12.1) into my React Native app (using Swift bridging for iOS) and have implemented full VoIP, PushKit, and CallKit support for incoming calls. ✅ What works: Incoming calls trigger the VoIP push and display the full-screen CallKit interface (or fallback UI). Decline Call works as expected. Call logs and events print correctly. ❌ Problem: When I try to accept the call using the CallKit Accept button or React Native fallback UI, I consistently get: ❌ [TwilioVoiceModule] answerCall() callInvite is missing. I also noticed that the console logs for answerCall() are being printed three times in a row, even though the accept button is only pressed once. Additionally in the first time console, answerCall() CallInvite found, accepting... 🔍 Observations: The callInvite is properly received when the VoIP push arrives. But when answerCall() is triggered, callInvite becomes nil. This happens in CallKit accept, RN UI accept, and even notification banner accept. 📦 How it's set up (summarized): PushKit Registration – via PKPushRegistry in AppDelegate.swift VoIP push handling – forwards payload to TwilioVoiceModule.handleIncomingPush() CallKit integration – uses CXProviderDelegate to report and handle accept actions JS Bridge – emits acceptCallAction to JS React Native calls TwilioVoiceModule.answerCall(uuid, callSid) In answerCall() method: self.callInvite is nil – so call cannot be accepted. Attaching the link to view the relevant code: https://docs.google.com/document/d/15pNjKrfk954OaotpMIEh3xQUtst---1K45DBXoYctGM/edit?usp=sharing 💡 Call Accept Flow (iOS): VoIP Push → TwilioVoiceModule.handleIncomingPush() Twilio SDK creates callInvite reportNewIncomingCall() triggers CallKit UI On accept: CXAnswerCallAction → emits event to JS RN calls TwilioVoiceModule.answerCall(uuid, callSid) Problem: callInvite is already nil ❓ What I'm trying to understand: Why is callInvite becoming nil before answerCall() is called? Why are the logs showing the answerCall() call 3 times? Is there a race condition or multiple accept triggers? Should I ensure callInvite is accepted only once across all 3 accept paths? ** 💬 Any help would be appreciated.** 📱 Environment: React Native 0.78.x iOS 17+ Swift bridging with TwilioVoiceModule.swift Twilio Voice SDK 6.12.1 PushKit + CallKit + react-native-callkeep
Replies
1
Boosts
0
Views
1.3k
Activity
Aug ’25
PAC ( Automatic Proxy Configuration ) Script Not working with Safari MacOS version 15.1
We have written a PAC script that blocklists certain domains and whitelists others. We went to Settings > Network > Wi-Fi (the network we are using), then clicked on Details, and under Proxies, we added the PAC file URL in the Automatic Proxy Configuration section. We tried hosting the PAC file both on localhost and on a separate HTTP server. After saving the settings, we tested several URLs. The blocking and allowing behavior works correctly in all browsers except Safari. Below is the PAC script we are using for your reference. The script works as expected in browsers other than Safari. This is how the PAC script URL looks: http://localhost:31290/proxy.pac function FindProxyForURL(url, host) { var blacklist = new Set(["facebook.com", "deepseek.com"]); var b_list = [...blacklist]; for (let i = 0; i < b_list.length; i++) { let ele = b_list[i] + "*"; if (shExpMatch(host, ele) || shExpMatch(url, ele)) { return "PROXY localhost:8086"; } } if (isIPBlocked(whitelist_subnet, hostIP)) { return "PROXY localhost:8087"; } if (isIPBlocked(blacklist_subnet, hostIP)) { return "PROXY localhost:8086"; } return "PROXY localhost:8080"; }
Replies
2
Boosts
0
Views
1.2k
Activity
Jul ’25