ultimate-jekyll-manager 1.3.5 → 1.3.6
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +7 -0
- package/dist/assets/js/libs/auth.js +10 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -14,6 +14,13 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/).
|
|
|
14
14
|
- `Fixed` for any bug fixes.
|
|
15
15
|
- `Security` in case of vulnerabilities.
|
|
16
16
|
|
|
17
|
+
---
|
|
18
|
+
## [1.3.6] - 2026-05-24
|
|
19
|
+
|
|
20
|
+
### Fixed
|
|
21
|
+
|
|
22
|
+
- **`auth/error-code:-47` now shows a friendly message instead of the raw FirebaseError.** v1.3.5's diagnostic confirmed: on the OAuth redirect path (`signInWithIdp` → 503), Firebase strips the BEM-side `HttpsError` message and delivers `code: 'auth/error-code:-47'` with `customData: {}` — empty. There's nothing to extract because Firebase ate the message client-side. This contradicts Firebase's own [Identity Platform docs](https://cloud.google.com/identity-platform/docs/blocking-functions) which describe a `BLOCKING_FUNCTION_ERROR_RESPONSE` wrapper that SHOULD carry the original message. The wrapper works on the 400 path (email signup, OAuth popup) — our v1.3.4 extractor handles that fine. The 503 path is broken: tracked at [firebase-js-sdk#8054](https://github.com/firebase/firebase-js-sdk/issues/8054), where a Firebase engineer said "503 seems to be the working as design error codes" then the issue was auto-closed as stale 5 weeks later without a fix or workaround. The `-47` code is 1:1 with "blocking-function rejected this signup," so `extractBlockingFunctionMessage()` now returns a generic-but-helpful message covering all three BEM `beforeCreate` reasons (rate limit, disposable email, custom hook reject): "Account creation is temporarily restricted. This can happen if you've recently created too many accounts, or your email is on our blocked list. Please try again later or contact support." The original `customData.serverResponse` path stays as the primary handler — the `-47` catchall is an additive fallback for when Firebase eats the message.
|
|
23
|
+
|
|
17
24
|
---
|
|
18
25
|
## [1.3.5] - 2026-05-24
|
|
19
26
|
|
|
@@ -816,6 +816,16 @@ export default function () {
|
|
|
816
816
|
fullError: error,
|
|
817
817
|
});
|
|
818
818
|
|
|
819
|
+
// The OAuth redirect path (signInWithIdp → 503) delivers the rejection as
|
|
820
|
+
// `auth/error-code:-47` with NO `customData.serverResponse` blob — Firebase
|
|
821
|
+
// strips the BEM-side message before it reaches the client. The code is
|
|
822
|
+
// 1:1 with "blocking-function rejected this signup," so surface a generic-
|
|
823
|
+
// but-helpful message that covers all three BEM beforeCreate reasons
|
|
824
|
+
// (rate limit, disposable email, custom hook reject).
|
|
825
|
+
if (error?.code === 'auth/error-code:-47') {
|
|
826
|
+
return 'Account creation is temporarily restricted. This can happen if you\'ve recently created too many accounts, or your email is on our blocked list. Please try again later or contact support.';
|
|
827
|
+
}
|
|
828
|
+
|
|
819
829
|
const raw = error?.customData?.serverResponse;
|
|
820
830
|
if (!raw) {
|
|
821
831
|
return null;
|