Polyfills 2.32.0 is a new update to PoomSmart's jailbreak tweak for bringing newer JavaScript and Web API behavior to older iOS WebKit environments. The official package metadata now lists version 2.32.0, supports iOS 8.0 and later, and describes the tweak as injecting JavaScript polyfills into iOS web views.
The update is especially relevant to people who continue using older jailbroken iPhones and iPads for web browsing. Modern websites increasingly assume that browsers provide APIs introduced long after early versions of Mobile Safari shipped. A polyfill does not replace Safari or WebKit; instead, it supplies JavaScript implementations for selected missing browser features so a site has a better chance of running as intended.
What's new in Polyfills 2.32.0
PoomSmart's official changelog for 2.32.0 adds another group of APIs across several generations of iOS. The version thresholds matter because the project is designed to add these implementations only where the corresponding WebKit environment needs them.
The release also adds WeakMap.getOrInsert and WeakMap.getOrInsertComputed for iOS versions before 26.2. That makes this release broader than a compatibility patch aimed only at very old iPhones: the project is also tracking newer JavaScript APIs that are absent from comparatively recent WebKit versions.
Why the fetch and URLSearchParams additions matter
Among the larger additions in 2.32.0 are the fetch family and URLSearchParams. The official changelog lists fetch, Headers, Request and Response for versions earlier than iOS 10.3. These interfaces form a common way for modern JavaScript applications to make network requests and work with responses. URLSearchParams provides a standardized interface for reading and constructing URL query parameters.
Older Safari releases predate these interfaces or lack the behavior newer sites expect. When a site assumes those objects exist and does not ship its own fallback, JavaScript can fail before the rest of the page has a chance to run. Polyfills attempts to fill selected gaps at the WebKit level on a jailbroken device.
TextEncoder, queueMicrotask and DOM compatibility
Version 2.32.0 also adds TextEncoder and TextDecoder for systems before iOS 10.3, while TextEncoder.encodeInto is covered on versions before iOS 14.5. These APIs convert between strings and encoded byte representations and are increasingly assumed by web libraries that process binary or structured data.
The release adds queueMicrotask before iOS 12.1 and Element.replaceChildren before iOS 14.0. These are smaller APIs than fetch, but modern frameworks and utility libraries can still expect them to exist. A missing method can be enough to break a specific workflow even when most of a website renders correctly.
Promise.any, AggregateError and AbortSignal
Another part of 2.32.0 focuses on Promise and cancellation-related APIs. The official changelog says Polyfills adds AggregateError and makes Promise.any reject with AggregateError on systems before iOS 14.0.
It also adds the static AbortSignal.abort, AbortSignal.timeout and AbortSignal.any methods with different cutoffs: before iOS 15.0, iOS 16.0 and iOS 17.4 respectively. Keeping those cutoffs separate is important; the update is not simply injecting every script into every version of iOS.
An interesting source-code detail: a ChatGPT-specific blacklist
The 2.32.0 commit adds chatgpt.com to the blacklist for oklch-fallback.js. The source commit does not provide a user-facing explanation for the exclusion, so we are not assigning a reason that the developer did not state.
This is a useful example of why we are using original sources for these articles rather than repeating package-index text. The code itself confirms that Polyfills can selectively avoid applying a particular compatibility script on a specific website. PoomSmart's broader project documentation also describes website and polyfill blacklisting as part of the tweak's design.
How Polyfills works
According to the official GitHub README, Polyfills targets Mobile Safari, Safari View Services and general WebKit-based views. The project organizes scripts into normal, priority and post-load groups. Priority scripts can run at document start before other polyfills, normal scripts can run at document start, and post scripts can wait until the document has loaded.
The project can also place scripts inside version-specific folders so they are used only on iOS versions at or below a defined threshold. That approach is important for a compatibility tweak: adding a workaround where the browser already has a complete native implementation can be unnecessary or create conflicts.
Will this make every modern website work on an old iPhone?
No. PoomSmart's own README is careful about this point. Polyfills can help when a website depends on JavaScript features or APIs that can realistically be recreated in JavaScript, but it cannot turn an old WebKit build into a completely current browser engine.
Some modern web standards depend on browser-engine behavior, CSS features, media codecs or APIs that do not have a practical JavaScript replacement. The project therefore describes website compatibility as case-dependent rather than promising that every broken website will be fixed.
Compatibility and dependencies
The current official package control file identifies the package as com.ps.polyfills, lists PoomSmart as author and maintainer, and sets the version to 2.32.0. The package declares firmware 8.0 or later and depends on MobileSubstrate, PreferenceLoader and the separate RegExp Polyfills package. The package metadata also contains a conditional dependency involving Custom Sec Headers.
Before installing or updating: verify the package identifier, developer, version and dependencies in your package manager against PoomSmart's official source. Next Jailbreak is not mirroring the package or linking to an unofficial copy.
Who should care about 2.32.0?
For people on very old iOS versions, the most significant additions are likely the fetch family, URLSearchParams and TextEncoder/TextDecoder because these are common building blocks in modern web applications. For users on later iOS releases, the update still includes targeted additions such as newer AbortSignal methods and WeakMap methods.
The key point is the version-specific approach. Polyfills 2.32.0 is not a blanket injection of the same compatibility code everywhere. The official changelog assigns different cutoffs to different APIs, and the source code contains logic for mapping related constructors and scripts to the environments that need them.
Next Jailbreak assessment
This is a useful release to cover because the source is unusually transparent. The current version is visible in the developer's package control file, the official depiction lists the full 2.32.0 changelog, and the August 30 GitHub commit shows the actual additions behind the version bump. That gives us much stronger evidence than simply reporting that a package index changed from 2.31.0 to 2.32.0.
If you already use Polyfills, read the official changelog before updating so you know which compatibility layers are new. If you do not use it, the tweak is mainly relevant when an older jailbroken device remains in service and websites fail because their JavaScript expects APIs that its WebKit version does not provide.
Original sources
- PoomSmart/Polyfills official GitHub repository
- Official Polyfills depiction and changelog
- August 30, 2026 source commit for version 2.32.0
Source-checked editorial article · Published August 31, 2026 · Next Jailbreak