Date objects should be able to be constructed with strings formatted as YYYY-MM-DD . On Chrome-based browsers, both of the following are valid: new Date("2022-06-01") new Date("2022-6-01") although the second one does not strictly follow the format. However, it is extremely convenient to work with since you do not have to check for the string length and determine whether to add a 0 in the beginning. Yet, on my Safari browser, the code: new Date("2022-6-01") returns a date object of an invalid date. This is simple to fix, yet it poses an inconvenience during development. Is there any way to let Apple improve its JavaScript engine?

Hello Apple Team, We are facing bunch of Crashes with our app especially on OS - 15.4.1 - iPad. Our Application Build in React Native. Below are our combination of Versions. React native Version - 0.67.2 iPad OS - 15.4.1 Please help us with the resolution. Few Crashes details - JavaScriptCore: WTFCrashWithInfo(int, char const*, char const*, int) + 20 Incident Identifier: AF04B559-ED71-4D37-970B-936A4B9C492D Hardware Model: iPad11,6 Process: HN MyClub [22228] Path: /private/var/containers/Bundle/Application/7BD07FFF-14C9-439A-BC82-B203D221F70C/HN MyClub.app/HN MyClub Identifier: com.herbalife.ncx.ordering Version: 1.0.104 (3153) AppStoreTools: 13F15 AppVariant: 1:iPad11,6:15 Code Type: ARM-64 (Native) Role: Foreground Parent Process: launchd [1] Coalition: com.herbalife.ncx.ordering [417] Date/Time: 2022-05-18 16:21:19.9925 -0500 Launch Time: 2022-05-18 15:21:17.4635 -0500 OS Version: iPhone OS 15.4.1 (19E258) Release Type: User Report Version: 104 Exception Type: EXC_BREAKPOINT (SIGTRAP) Exception Codes: 0x0000000000000001, 0x000000018bda95c4 Exception Note: EXC_CORPSE_NOTIFY Triggered by Thread: 8 Thread 0 name: Thread 0: 0 libsystem_kernel.dylib 0x00000001b75dc4e0 mach_msg_trap + 8 1 libsystem_kernel.dylib 0x00000001b75dcb24 mach_msg + 76 (mach_msg.c:119) 2 CoreFoundation 0x0000000180804820 __CFRunLoopServiceMachPort + 372 (CFRunLoop.c:2646) 3 CoreFoundation 0x0000000180808cac __CFRunLoopRun + 1180 (CFRunLoop.c:3000) 4 CoreFoundation 0x000000018081c6b8 CFRunLoopRunSpecific + 600 (CFRunLoop.c:3268) 5 GraphicsServices 0x000000019c8b6374 GSEventRunModal + 164 (GSEvent.c:2200) 6 UIKitCore 0x0000000183181e88 -[UIApplication _run] + 1100 (UIApplication.m:3511) 7 UIKitCore 0x0000000182f035ec UIApplicationMain + 364 (UIApplication.m:5064) 8 HN MyClub 0x0000000104dab974 main + 68 (AppDelegate.swift:17) 9 dyld 0x0000000105465ce4 start + 520 (dyldMain.cpp:879) Another Crash Incident Identifier: 412D9D60-97E1-492D-AEEB-D1B360DFCA72 CrashReporter Key: 920e264a09d2674e3e297b9b826ad4cc2ee24a8c Hardware Model: iPad12,1 Process: HN MyClub [42004] Path: /private/var/containers/Bundle/Application/AD416DD9-2515-4AD8-99C4-5D91F71600F7/HN MyClub.app/HN MyClub Identifier: com.herbalife.ncx.ordering Version: 3153 (1.0.104) Code Type: ARM-64 Parent Process: ? [1] Date/Time: 2022-05-24 11:02:58.148 -0500 OS Version: iPadOS 15.4.1 (19E258) Report Version: 104 Exception Type: EXC_BREAKPOINT (SIGTRAP) Exception Codes: 0x00000000 at 0x000000018bd9d5c4 Crashed Thread: 19 Thread 0: 0 libsystem_kernel.dylib 0x00000001b75d04e0 0x1b75cf000 + 5344 (mach_msg_trap + 8) 1 libsystem_kernel.dylib 0x00000001b75d0b24 0x1b75cf000 + 6948 (mach_msg + 76) 2 CoreFoundation 0x00000001807f8820 0x1807f1000 + 30752 (<redacted> + 372) 3 CoreFoundation 0x00000001807fccac 0x1807f1000 + 48300 (<redacted> + 1180) 4 CoreFoundation 0x00000001808106b8 0x1807f1000 + 128696 (CFRunLoopRunSpecific + 600) 5 GraphicsServices 0x000000019c8aa374 0x19c8a9000 + 4980 (GSEventRunModal + 164) 6 UIKitCore 0x0000000183175e88 0x182c62000 + 5324424 (<redacted> + 1100) 7 UIKitCore 0x0000000182ef75ec 0x182c62000 + 2708972 (UIApplicationMain + 364) 8 HN MyClub 0x0000000102c0f974 0x102c08000 + 31092 9 (null) 0x0000000103349ce4 0x0 + 4348746980 Notable Addresses: { "stack@0x2a1e8fc78": { "address": 6658003453, "type": "string", "value": "void ***::StringBuilder::reifyString() const" }, "stack@0x2a1e8fc80": { "address": 6658003373, "type": "string", "value": "/Library/Caches/com.apple.xbs/Sources/***/Source/***/***/text/StringBuilder.cpp" }, "x1": { "address": 6658003373, "type": "string", "value": "/Library/Caches/com.apple.xbs/Sources/***/Source/***/***/text/StringBuilder.cpp" }, "x2": { "address": 6658003453, "type": "string", "value": "void ***::StringBuilder::reifyString() const" } } Application Stats: { "active_time_since_last_crash": 76929.9, "active_time_since_launch": 76929.9, "application_active": true, "application_in_foreground": true, "background_time_since_last_crash": 97308.6, "background_time_since_launch": 97308.6, "launches_since_last_crash": 0, "sessions_since_last_crash": 7, "sessions_since_launch": 7 } If any one has an idea what is this crash about or some a clue that help me to continue looking for the specific root issue, I would really appreciate it a lot. Thanks!!

Hi there, I'm experiencing several crashes on JavaScriptCore pas_panic_on_out_of_memory_error, only on devices with tvOS 15.4 and 15.4.1. This happens with users using the app for several hours as well as 5 seconds after launching the app. Devices: AppleTV6,2 and AppleTV5,3 Thread 14 — JavaScriptCore pas_panic_on_out_of_memory_error (JavaScriptCore) JavaScriptCore bmalloc_try_iso_allocate_impl_impl_slow (JavaScriptCore) JavaScriptCore bmalloc_heap_config_specialized_local_allocator_try_allocate_small_segregated_slow (JavaScriptCore) JavaScriptCore bmalloc_allocate_impl_casual_case (JavaScriptCore) JavaScriptCore ***::String::String(char16_t const*, unsigned int) (JavaScriptCore) JavaScriptCore JSC::LiteralParser<char16_t>::parsePrimitiveValue(JSC::VM&) (JavaScriptCore) JavaScriptCore JSC::LiteralParser<char16_t>::parse(JSC::ParserState) (JavaScriptCore) JavaScriptCore JSC::jsonProtoFuncParse(JSC::JSGlobalObject*, JSC::CallFrame*) (JavaScriptCore) JavaScriptCore llint_entry (JavaScriptCore) JavaScriptCore llint_entry (JavaScriptCore) JavaScriptCore llint_entry (JavaScriptCore) JavaScriptCore llint_entry (JavaScriptCore) JavaScriptCore vmEntryToJavaScript (JavaScriptCore) JavaScriptCore JSC::Interpreter::executeCall(JSC::JSGlobalObject*, JSC::JSObject*, JSC::CallData const&, JSC::JSValue, JSC::ArgList const&) (JavaScriptCore) JavaScriptCore JSC::boundThisNoArgsFunctionCall(JSC::JSGlobalObject*, JSC::CallFrame*) (JavaScriptCore) JavaScriptCore vmEntryToNative (JavaScriptCore) JavaScriptCore JSC::Interpreter::executeCall(JSC::JSGlobalObject*, JSC::JSObject*, JSC::CallData const&, JSC::JSValue, JSC::ArgList const&) (JavaScriptCore) JavaScriptCore JSC::profiledCall(JSC::JSGlobalObject*, JSC::ProfilingReason, JSC::JSValue, JSC::CallData const&, JSC::JSValue, JSC::ArgList const&) (JavaScriptCore) JavaScriptCore JSObjectCallAsFunction (JavaScriptCore) JavaScriptCore -[JSValue invokeMethod:withArguments:] (JavaScriptCore) ITMLKit -[IKJSObject invokeMethod:withArguments:] (ITMLKit) ITMLKit -[IKJSEventListenerObject invokeMethod:withArguments:thenDispatchEvent:extraInfo:] (ITMLKit) ITMLKit __43-[IKJSXMLHTTPRequest setRequestReadyState:]_block_invoke (ITMLKit) ITMLKit -[IKAppContext _doEvaluate:] (ITMLKit) ITMLKit -[IKAppContext _evaluate:] (ITMLKit) ITMLKit __41-[IKAppContext evaluate:completionBlock:]_block_invoke (ITMLKit) ITMLKit -[IKAppContext _sourcePerform] (ITMLKit) ITMLKit -[IKConcurrentEvaluator lockSchedulingForEvaluation:] (ITMLKit) ITMLKit IKRunLoopSourcePerformCallBack (ITMLKit) CoreFoundation __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ (CoreFoundation) CoreFoundation __CFRunLoopDoSource0 (CoreFoundation) CoreFoundation __CFRunLoopDoSources0 (CoreFoundation) CoreFoundation __CFRunLoopRun (CoreFoundation) CoreFoundation CFRunLoopRunSpecific (CoreFoundation) ITMLKit -[IKAppContext _jsThreadMain] (ITMLKit) Foundation __NSThread__start__ (Foundation) libsyste...ad.dylib _pthread_start (libsystem_pthread.dylib) libsyste...ad.dylib thread_start (libsystem_pthread.dylib) This issue seems very similar to this existing thread, although not sure its related

After iOS15.4 was released, we noticed the issue. It seems a system bug. It's waiting for the lock for a long time(dead lock). Hardware Model: iPhone13,3 Process: app [9492] Path: /private/var/containers/Bundle/Application/***/app.app/app Identifier: com.aaa.app AppStoreTools: 13C90b AppVariant: 1:iPhone13,3:15 Code Type: ARM-64 (Native) Role: Foreground Parent Process: launchd [1] Coalition: com.aaa.app [956] Date/Time: 2022-03-17 18:04:46.2811 +0800 Launch Time: 2022-03-17 17:35:18.7389 +0800 OS Version: iPhone OS 15.4 (19E241) Release Type: User Baseband Version: 2.53.01 Report Version: 104 Exception Type: EXC_CRASH (SIGKILL) Exception Codes: 0x0000000000000000, 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY Termination Reason: FRONTBOARD 2343432205 &lt;RBSTerminateContext| domain:10 code:0x8BADF00D explanation:scene-update watchdog transgression: application&lt;com.aaa.app&gt;:9492 exhausted real (wall clock) time allowance of 10.00 seconds ProcessVisibility: Background ProcessState: Running WatchdogEvent: scene-update WatchdogVisibility: Background WatchdogCPUStatistics: ( "Elapsed total CPU time (seconds): 20.970 (user 13.070, system 7.900), 35% CPU", "Elapsed application CPU time (seconds): 0.829, 1% CPU" ) reportType:CrashLog maxTerminationResistance:Interactive&gt; Triggered by Thread: 0 Kernel Triage: VM - pmap_enter failed with resource shortage VM - pmap_enter failed with resource shortage Thread 0 name: Thread 0 Crashed: 0 libsystem_kernel.dylib 0x00000001cddd1178 __ulock_wait + 8 1 libsystem_platform.dylib 0x0000000207a399ac _os_unfair_lock_lock_slow + 172 (lock.c:578) 2 JavaScriptCore 0x00000001a26f1c38 pas_page_sharing_pool_take_least_recently_used + 800 (lock_private.h:684) 3 JavaScriptCore 0x00000001a26f2cf4 pas_physical_page_sharing_pool_take + 248 (pas_page_sharing_pool.c:716) 4 JavaScriptCore 0x00000001a26ca2ec bmalloc_medium_bitfit_page_config_specialized_allocator_try_allocate + 260 (pas_page_sharing_pool.c:862) 5 JavaScriptCore 0x00000001a26cf48c bmalloc_heap_config_specialized_local_allocator_try_allocate_slow + 328 (pas_local_allocator_inlines.h:1595) 6 JavaScriptCore 0x00000001a26ba39c bmalloc_allocate_impl_casual_case + 888 (pas_local_allocator_inlines.h:1796) 7 JavaScriptCore 0x00000001a19d6fb8 ***::RobinHoodHashTable&lt;***::RefPtr&lt;***::UniquedStringImpl, ***::RawPtrTraits&lt;***::UniquedStringImpl&gt;, ***::DefaultRefDerefTraits&lt;***::UniquedStringImpl&gt; &gt;, ***::KeyValuePair&lt;***::RefPtr&lt;***::Uniqu... + 52 (FastMalloc.h:219) 8 JavaScriptCore 0x00000001a19c6a2c ***::HashTableAddResult&lt;***::HashTableIterator&lt;***::RobinHoodHashTable&lt;***::RefPtr&lt;***::UniquedStringImpl, ***::RawPtrTraits&lt;***::UniquedStringImpl&gt;, ***::DefaultRefDerefTraits&lt;***::UniquedStringIm... + 140 (RobinHoodHashTable.h:729) 9 JavaScriptCore 0x00000001a19c3dac JSC::BytecodeIntrinsicRegistry::BytecodeIntrinsicRegistry(JSC::VM&amp;) + 33204 (BytecodeIntrinsicRegistry.cpp:59) 10 JavaScriptCore 0x00000001a23931fc JSC::VM::VM(JSC::VM::VMType, JSC::HeapType, ***::RunLoop*, bool*) + 11444 (unique_ptr.h:728) 11 JavaScriptCore 0x00000001a2395fd8 JSC::VM::createContextGroup(JSC::HeapType) + 52 (VM.cpp:241) 12 JavaScriptCore 0x00000001a1811dc0 JSContextGroupCreate + 32 (JSContextRef.cpp:70) 13 JavaScriptCore 0x00000001a14aa2a4 -[JSVirtualMachine init] + 24 (JSVirtualMachine.mm:94) 14 JavaScriptCore 0x00000001a14aa304 -[JSContext init] + 32 (JSContext.mm:71) 15 WebKit 0x00000001a5058b94 API::SharedJSContext::ensureContext() + 56 (APISerializedScriptValueCocoa.mm:51) 16 WebKit 0x00000001a5058ad4 API::SerializedScriptValue::deserialize(WebCore::SerializedScriptValue&amp;, OpaqueJSValue const**) + 44 (APISerializedScriptValueCocoa.mm:78) 17 WebKit 0x00000001a50d7180 ScriptMessageHandlerDelegate::didPostMessage(WebKit::WebPageProxy&amp;, WebKit::FrameInfoData&amp;&amp;, API::ContentWorld&amp;, WebCore::SerializedScriptValue&amp;) + 136 (WKUserContentController.mm:152) 18 WebKit 0x00000001a5424da4 WebKit::WebUserContentControllerProxy::didPostMessage(***::ObjectIdentifier&lt;WebKit::WebPageProxyIdentifierType&gt;, WebKit::FrameInfoData&amp;&amp;, unsigned long long, ***::Span&lt;unsigned char const, 18446744... + 732 (WebUserContentControllerProxy.cpp:346) 19 WebKit 0x00000001a5708dcc WebKit::WebUserContentControllerProxy::didReceiveMessage(IPC::Connection&amp;, IPC::Decoder&amp;) + 2716 (HandleMessage.h:139) 20 WebKit 0x00000001a5159b60 IPC::MessageReceiverMap::dispatchMessage(IPC::Connection&amp;, IPC::Decoder&amp;) + 264 (MessageReceiverMap.cpp:129) 21 WebKit 0x00000001a5381dac WebKit::WebProcessProxy::didReceiveMessage(IPC::Connection&amp;, IPC::Decoder&amp;) + 40 (AuxiliaryProcessProxy.cpp:247) 22 WebKit 0x00000001a514e2ac IPC::Connection::dispatchMessage(std::__1::unique_ptr&lt;IPC::Decoder, std::__1::default_delete&lt;IPC::Decoder&gt; &gt;) + 788 (Connection.cpp:1080) 23 WebKit 0x00000001a514d960 IPC::Connection::dispatchIncomingMessages() + 508 (Connection.cpp:1229) 24 JavaScriptCore 0x00000001a265de10 ***::RunLoop::performWork() + 200 (Function.h:82) 25 JavaScriptCore 0x00000001a265ebac ***::RunLoop::performWork(void*) + 36 (RunLoopCF.cpp:46) 26 CoreFoundation 0x000000019632ff04 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 28 (CFRunLoop.c:1972) 27 CoreFoundation 0x0000000196340c90 __CFRunLoopDoSource0 + 208 (CFRunLoop.c:2016) 28 CoreFoundation 0x000000019627a184 __CFRunLoopDoSources0 + 268 (CFRunLoop.c:2053) 29 CoreFoundation 0x000000019627fb4c __CFRunLoopRun + 828 (CFRunLoop.c:2951) 30 CoreFoundation 0x00000001962936b8 CFRunLoopRunSpecific + 600 (CFRunLoop.c:3268) 31 GraphicsServices 0x00000001b232d374 GSEventRunModal + 164 (GSEvent.c:2200) 32 UIKitCore 0x0000000198bf8e88 -[UIApplication _run] + 1100 (UIApplication.m:3511) 33 UIKitCore 0x000000019897a5ec UIApplicationMain + 364 (UIApplication.m:5064) 34 app 0x0000000104cd277c main + 388 (main.mm:38) 35 dyld 0x0000000109919ce4 start + 520 (dyldMain.cpp:879)

How do I use an NPM javascript package inside of a SwiftUI program? I'm trying to use functions from a package with only one javascript file inside of it for data in an app I am trying to make in SwiftUI. I know that I can use JavaScriptCore to run JavaScript code, but how can I refer to these functions inside of my project. Currently I have an empty project, and I want to use this package to display basic data on a SwiftUI View. If it helps, the package is linked here: [https://github.com/DavidAngell/Aspen-SIS#readme)

Hello, I'm trying to launch some JS code, and it's using atob function from js. But when I launch code in swift with JSContext, I have an error ReferenceError: Can't find variable: atob. What can I do to solve this?

Here I'm initiating the JS call from swift and based on the results app UI gets updated. Since this method is time taking process it freezes the app for a few seconds and becomes normal. We can understand it's running in the main thread so blocked the UI. I have tried to run it in the background using the below code and it doesn't work. DispatchQueue.global(qos: .background).async { let fn = engineJSContext?.objectForKeyedSubscript("jsMethodName") let val = fn?.call(withArguments: [params1, params2]) } As per the document , we can run it from any thread, but I'm facing a problem on the background thread . Any help on this please.

Greetings, I have an app that relies on WKWebView and it works fine in iOS 15.1. However I've noticed that the WKWebView hangs in all the iOS 15.2 betas after approximately 20 seconds. At this point my only recourse is to recreate the WKWebView, as it no longer accepts any javascript. The remainder of the app behaves normally. Has anyone else experienced this and have any suggestions? My app updates the WKWebview approximately every second. However even without updating it, interacting with javascript running on it also causes it to lock up. Hitting the pause button on Xcode reveals that the JavaScriptCode malloc scavenger's last instruction is 0_psynch_cwait, but then again pausing the app when the WKWebView is not hanging reveals the same so, it's not a good clue. Thank you, SalCat

I have some code that relies on WebSocket to connect a device: t = new WebSocket(this.getUrl()); But I get an error: [JS Exception] ReferenceError: Can't find variable: WebSocket The Logic Pro X Scripter documentation states: The version of JavaScript used by the Scripter plug-in is determined by the JavaScriptCore framework version installed on your system.  How do I determine which version of JavaScript is being used by the JavascriptCore framework? Is there an alternative to WebSocket available in the Scripter javascript engine?

Application is hosted on web kit, after iOS 15 upgrade, select dropdown triggering error. "[Assert] Failed to present a context menu for configuration with identifier ***. This is likely due to a different presentation occuring during the lifecycle of the interaction."

I'm using this js package  https://www.npmjs.com/package/idb to manage a simple indexedDB implementation on a web app. I'm using the excellent https://www.npmjs.com/package/idb package to manage a simple indexedDB implementation on a web app. I'm having this error "UnknownError: Database deleted by request of the user" reported to our error reporting system for a significant number of iOS users and I'm having trouble replicating. It seems to have so far only affect users on: Mobile Safari 14.6, 14.4.2, caught by try/catch Instagram webview, iOS 14.7.1 - not caught be try/catch I think the source of the error is this line in webkit https://github.com/WebKit/WebKit/blob/e98ff129bc8eba06ac17105f19c5f0e142aab853/Source/WebCore/Modules/indexeddb/shared/IDBError.h#L40 It seems to relate to the server connection closing. Can anyone help me understand what conditions are required to trigger this error so that I can replicate and try to handle in the app? A simplified version of the implementation: // ./store.js import { openDB } from 'idb' export const upgrade = (db) => { if (!db?.createObjectStore) return null db.createObjectStore('example_store_name_1') } export const set = async (storeName, val, key) => { const dbPromise = openDB('example_db_name', 1, { upgrade }) if (!window.indexedDB) return null return (await dbPromise).put(storeName, val, key) } export const count = async (storeName) => { const dbPromise = openDB('example_db_name', 1, { upgrade }) if (!window.indexedDB) return null return (await dbPromise).count(storeName) } // ./index.js import { set, count } from './store.js' export const storeEvent = async (storeName, value, key) => { try { const rowCount = await count(storeName) // I process and clear the db in a separate part of the app, this count is just here here as a rough limit to // ensure that I don't keep pushing data into storage if, for some reason, it is not getting cleared elsewhere if (rowCount < 500) { await set(storeName, value, key) } } catch (error) { // error reported to error monitoring tool } } Some of the things I have tried to replicate (on Instagram webveiw, iOS 14.7.1 or Mobile Safari 14.6): saving a massive object to idb and closing or backgrounding Instagram or Safari mid transaction saving a massive object to idb across multiple Safari tabs at the same time manually deleting idb db from Safari while transaction is in progress - seems to generate either "UnknownError: * Connection is closing." or "AbortError: The transaction was aborted, so the request cannot be fulfilled." - both caught by try/catch Safari incognito Setting Safari privacy to store no cookies (or any other form of browser storage) this transaction lifetime bug https://github.com/jakearchibald/idb#transaction-lifetime ... Google - nothing for this error other than the webkit source code. Any suggestions appreciated. I'd like to understand particularly how it is triggered in the iOS webview (Instagram) as these errors are not caught by try/catch currently.

I have a JavaScriptCore scripting interface in my app. After migrating to Big Sur, I'm getting constant crashes after the context has already been abandoned and all of the code evaluated. I have multiple JSContext instances, each with their own virtual machine, one created for all of the scripts separately. I'm getting both general protection faults (EXC_I386_GPFLT) and more general bad access crashes (ie. Heap Helper Thread (30): EXC_BAD_ACCESS (code=1, address=0x7ffdde3bdf0) I'm guessing that something somewhere tries to access stuff that is no longer there, even though this shouldn't happen as any execution has already ended. Is there a way to create some sort of protection against this, and how do I effectively debug these errors? Can't really step into evaluated JavaScript :-) Also, is there a way to effectively null the context and VM after execution to tell them that they are no longer needed?

Dose Apple have any official documentation to study HTML/CSS/JavaScript ? Kind Regards

My iOS app is crashing on the initial load. It's happening both in my Testflight build and also in the production version of the app on the App Store. It was working fine a few days ago; this just started happening all of a sudden. What's strange is that after doing a fresh install, it doesn't happen the first time I open the app. It only happens after I force close the app and open it again (and every time afterward). I'm using Expo and React Native to build the app. I've attached a crash log. crash log - https://developer.apple.com/forums/content/attachment/6a5962a1-56ac-44b0-8ec4-4e8dee0daee8