[{"data":1,"prerenderedAt":688},["ShallowReactive",2],{"search-dialog-posts":3,"post-\u002Fposts\u002Fios-iframe-google-login-blank-page":316,"post-surround-\u002Fposts\u002Fios-iframe-google-login-blank-page":681},[4,12,21,29,37,47,57,67,77,85,96,104,112,121,129,137,147,155,164,173,181,188,195,207,215,224,236,241,247,254,260,266,272,279,286,291,298,304,310],{"path":5,"title":6,"description":7,"category":8,"tags":9},"\u002Fposts\u002Fgit-commands-cheatsheet","Git 常用指令與終端機筆記","2018 年整理的 Git 學習筆記，包含基本終端機指令、Git 操作、分支、reset、SourceTree、Vim 與一些常用設定。","notes",[10,11],"Git","版本控制",{"path":13,"title":14,"description":15,"category":16,"tags":17},"\u002Fposts\u002Fjs-prototype-inheritance","JavaScript 物件導向：建構函式、prototype 與繼承三步驟","整理 ES5 時代用建構函式加 prototype 手刻物件導向的完整流程——封裝屬性與方法、共用函式為什麼要掛在 prototype 上、以及繼承的三個步驟（call 借用母類別建構子、Object.create 接上原型鏈、修正 constructor 指向），並附上物件縮寫與計算屬性這兩個順便學到的 ES6 寫法。","frontend",[18,19,20],"JavaScript","物件導向","prototype",{"path":22,"title":23,"description":24,"category":16,"tags":25},"\u002Fposts\u002Fflexbox-notes","Flexbox 對齊與彈性尺寸筆記","記錄 Flexbox 的主軸與交錯軸對齊、flex-direction、flex-wrap，以及 flex-grow、flex-shrink、flex-basis 等常用屬性。",[26,27,28],"CSS","Flexbox","版面",{"path":30,"title":31,"description":32,"category":16,"tags":33},"\u002Fposts\u002Fscreen-orientation-api","screen.orientation：現在判斷與鎖定螢幕方向的做法","整理現在 JavaScript 判斷螢幕方向的方式，包括 screen.orientation、change 事件與 lock()，並說明 RWD 使用 matchMedia 或 CSS orientation 會更適合。",[18,34,35,36],"RWD","螢幕方向","PWA",{"path":38,"title":39,"description":40,"category":16,"tags":41},"\u002Fposts\u002Fpinia-vuex-state-management","Pinia \u002F Vuex 狀態管理及差異","紀錄 Vuex、Pinia 的狀態管理概念、差異與用法。",[42,43,44,45,46],"Pinia","Vuex","Vue3","狀態管理","Nuxt",{"path":48,"title":49,"description":50,"category":8,"tags":51},"\u002Fposts\u002Fpyenv-python-version-management","Python 多版本管理 pyenv","紀錄 macOS 與 Windows 使用 pyenv 管理 Python 版本的方式。",[52,53,54,55,56],"Python","pyenv","macOS","Windows","版本管理",{"path":58,"title":59,"description":60,"category":8,"tags":61},"\u002Fposts\u002Fnpm-publish-vue2-component","npm 發布流程","紀錄 Vue 2 元件的 npm 發布、dist-tag 與打包流程。",[62,63,64,65,66],"npm","Vue2","Vue CLI","套件發布","MIT",{"path":68,"title":69,"description":70,"category":8,"tags":71},"\u002Fposts\u002Fmobile-debugging-today","現在怎麼 debug 手機網頁：從裝一堆工具到幾乎不用裝","對照 2022 年那套 scoop、iTunes、remotedebug-ios-webkit-adapter 的繁瑣設定，整理現在偵錯手機網頁的做法：Android 無線偵錯、iOS 的實際選項、on-device console、Playwright 裝置模擬，以及本機 HTTPS 的處理。",[72,73,74,75,76],"debug","iOS","Android","Chrome DevTools","Playwright",{"path":78,"title":79,"description":80,"category":16,"tags":81},"\u002Fposts\u002Fplaywright-vs-cypress","E2E 測試現在選什麼：Playwright 與 Cypress 的實際差異","對照幾年前用 Cypress 的做法，說明 Playwright 為什麼變成多數新專案的預設選擇：真正的多瀏覽器支援、免費的平行執行、trace viewer 除錯，以及兩者在架構上的根本差異與各自仍然適合的場景。",[76,82,83,84],"Cypress","E2E","測試",{"path":86,"title":87,"description":88,"category":89,"tags":90},"\u002Fposts\u002Fjs-encoding-today","現在處理編碼：TextEncoder、Uint8Array 的 Base64 方法與 URLSearchParams","整理 JavaScript 現代編碼方式，使用 TextEncoder、TextDecoder 與 Uint8Array 處理 UTF-8 與 Base64，並說明 Base64URL、URLSearchParams 與 encodeURIComponent 的差異。","research",[91,92,93,94,95,18],"編碼","TextEncoder","Base64","URLSearchParams","Uint8Array",{"path":97,"title":98,"description":99,"category":16,"tags":100},"\u002Fposts\u002Fdart-sass-migration","Dart Sass 遷移筆記：node-sass 之後怎麼裝 Sass","node-sass 與 LibSass 已停止維護，現在改用 Dart Sass。整理 webpack 與 Vite 的安裝方式，以及為什麼不再像 node-sass 一樣容易遇到 Node.js 版本與原生編譯問題。",[101,102,103],"Sass","Webpack","Vite",{"path":105,"title":106,"description":107,"category":16,"tags":108},"\u002Fposts\u002Fdayjs-vue3-computed","day.js 搭配 Vue 3 的日期格式化","整理 Vue 3 日期格式化的常見做法，使用 day.js 取代舊專案常見的 moment.js，並以 method 或 computed 取代 Vue 2 filter，也補充原生 Intl.DateTimeFormat 的使用方式。",[44,109,110,111],"day.js","日期","Intl",{"path":113,"title":114,"description":115,"category":16,"tags":116},"\u002Fposts\u002Fes-modules-today","ES Module 現在的樣子：Node ESM、exports 與 import maps","整理現代 JavaScript ES Module 的常見用法，包括 Node.js 原生 ESM、package.json exports、瀏覽器 import maps、JSON import attributes，以及 Vite 動態載入的注意事項。",[117,118,119,120,103,18],"ES Module","Node.js","import maps","exports",{"path":122,"title":123,"description":124,"category":89,"tags":125},"\u002Fposts\u002Fstructured-clone","structuredClone()：終於有內建的深層拷貝","整理 JavaScript structuredClone() 的深層拷貝用法，說明 Date、Map、Set、循環參考的處理方式，以及 Function、class 與 Vue reactive Proxy 的注意事項。",[18,126,127,128],"structuredClone","深拷貝","Vue",{"path":130,"title":131,"description":132,"category":16,"tags":133},"\u002Fposts\u002Fdynamic-import","JavaScript 動態載入：import() 與 Vue 非同步元件","整理靜態 import、動態 import() 與 Vue defineAsyncComponent 的使用方式，並簡單補充 Vite import.meta.glob 的用途。",[18,134,135,103,136],"ES Modules","Vue 3","Code Splitting",{"path":138,"title":139,"description":140,"category":16,"tags":141},"\u002Fposts\u002Fscreen-wake-lock-api","Screen Wake Lock API：不用套件也能讓頁面保持亮著","整理 Screen Wake Lock API 的基本用法，說明 HTTPS、頁面可見性、切換分頁後重新取得 wake lock，以及 Vue／Nuxt 計時器使用時的注意事項。",[142,128,143,144,145,146],"Wake Lock","Nuxt4","行動裝置","計時器","Web API",{"path":148,"title":149,"description":150,"category":16,"tags":151},"\u002Fposts\u002Fhtml-meta-boilerplate-today","現在的 HTML meta 標籤怎麼寫","整理現在一個新頁面該有的 meta 標籤骨架——viewport 補上 viewport-fit=cover 因應瀏海與圓角螢幕、color-scheme 讓表單控制項跟著深色模式換色、theme-color 決定行動瀏覽器工具列顏色，以及基本的 SEO 與 Open Graph 標籤。",[152,153,154],"HTML","meta","SEO",{"path":156,"title":157,"description":158,"category":8,"tags":159},"\u002Fposts\u002Fdocker-node-postgres","把 Node + PostgreSQL 的 backend 裝進 Docker：Dockerfile、.dockerignore 與 compose","從「本機裝了就跑」到打包成容器的通用做法——Dockerfile 每一行的理由與 layer cache 為什麼決定了指令順序、.dockerignore 漏掉 node_modules 對原生模組是災難級的問題、容器之間為什麼不能用 localhost 互相找到對方，以及怎麼驗證資料真的寫進了 volume。",[160,161,118,162,163],"Docker","Docker Compose","PostgreSQL","Express",{"path":165,"title":166,"description":167,"category":16,"tags":168},"\u002Fposts\u002Fnuxt-server-proxy","Nuxt 3 \u002F 4 用 Server API 做代理與轉發","整理 Nuxt 3 與 Nuxt 4 使用 server\u002Fapi 轉發第三方 API 的方式，可以避免瀏覽器 CORS 問題、隱藏 API Key，也能在伺服器端加入快取。",[169,143,170,171,172],"Nuxt3","CORS","Nitro","API",{"path":174,"title":175,"description":176,"category":16,"tags":177},"\u002Fposts\u002Fnuxt4-project-setup","Nuxt 4 建立專案：和 Nuxt 3 有哪些不同","整理 Nuxt 4 建立專案的基本流程與目錄結構，並對照 Nuxt 3 的差異，包括 app\u002F 目錄、路徑別名、TypeScript，以及目前常用的 ESLint 與 Tailwind CSS 4 設定。",[143,44,178,179,180],"TypeScript","ESLint","Tailwind CSS 4",{"path":182,"title":183,"description":184,"category":16,"tags":185},"\u002Fposts\u002Fnuxt3-route-middleware","Nuxt 3 \u002F 4 的 Route Middleware：進頁面前先做判斷","整理 Nuxt 3 與 Nuxt 4 的 Route Middleware，用 defineNuxtRouteMiddleware 在進入頁面前檢查登入狀態，搭配 navigateTo 重新導向，並說明一般 middleware、global middleware 與 definePageMeta 的用法。",[169,143,186,187],"Middleware","驗證",{"path":189,"title":190,"description":191,"category":16,"tags":192},"\u002Fposts\u002Fnuxt-route-rules-redirect","Nuxt 3 \u002F 4 的 routeRules：重新導向與頁面設定","整理 Nuxt 3 與 Nuxt 4 的 routeRules 用法，可以依照不同網址設定重新導向、預渲染、SSR 與快取，並簡單對照 Nuxt 2 的舊做法。",[169,143,193,194],"routeRules","重新導向",{"path":196,"title":197,"description":198,"category":16,"tags":199},"\u002Fposts\u002Fios-iframe-google-login-blank-page","iOS iframe 串接 Google 登入出現空白頁：Popup 與頁面回收問題排查紀錄","記錄 iframe 內串接 Google 第三方登入時，部分 iOS 裝置因背景頁面遭到回收並重新載入，導致 Popup 登入流程中斷，以及最後透過 Redirect 分流與登入狀態接回機制處理的過程。",[73,200,201,202,203,204,205,206],"Safari","iframe","Google Login","GIS","OAuth","Popup","Redirect",{"path":208,"title":209,"description":210,"category":16,"tags":211},"\u002Fposts\u002Fios-login-tab-return-behavior","iOS 第三方登入後回不到原頁？分頁開啟關係與回頁行為實測","記錄 iOS Safari 與 Chrome 在多分頁第三方登入流程中，登入頁關閉後不一定回到原頁的實測，以及分頁開啟關係、window.close 與 window.focus 的限制。",[73,200,212,202,204,201,213,214],"Chrome","window.close","window.focus",{"path":216,"title":217,"description":218,"category":16,"tags":219},"\u002Fposts\u002Fgoogle-app-about-blank-placeholder","Google App 內建瀏覽器：about:blank 佔位頁被關閉的排查紀錄","記錄 iOS Google App 內建瀏覽器在非同步開啟外部頁面時，about:blank 佔位分頁被自動關閉，導致第三方登入或外部導轉失敗的排查與解法。",[73,220,221,222,204,223],"Google App","window.open","about:blank","WebView",{"path":225,"title":226,"description":227,"category":228,"tags":229},"\u002Fposts\u002Fclaude-code-codex-cli-init-basics","AI 相關紀錄 v1｜Claude Code \u002F Codex CLI 初始化與基本概念","從 Claude Code 與 Codex CLI 開始，整理 CLI、Coding Agent、Context、\u002Finit 與 CLAUDE.md／AGENTS.md 這幾個一開始最容易搞混的概念，以及在既有專案中的安裝與啟動方式。","ai",[230,231,232,233,234,235],"AI","Claude Code","Codex CLI","Coding Agent","CLAUDE.md","AGENTS.md",{"path":237,"title":238,"description":239,"category":228,"tags":240},"\u002Fposts\u002Fclaude-agents-md-project-guidelines","AI 相關紀錄 v2｜CLAUDE.md \u002F AGENTS.md 怎麼寫？專案規範與實際範例","整理 CLAUDE.md 與 AGENTS.md 的用途、適合記錄的專案規範，以及可直接參考的設定範例。",[230,231,232,234,235],{"path":242,"title":243,"description":244,"category":228,"tags":245},"\u002Fposts\u002Fclaude-codex-config-locations","AI 相關紀錄 v3｜Claude Code `.claude\u002F` \u002F Codex CLI 設定位置：全域與專案設定基本概要介紹","整理 Claude Code 與 Codex CLI 的使用者層級、專案層級設定位置，以及 rules、skills、agents 等目錄的用途。",[230,231,232,246],"設定檔",{"path":248,"title":249,"description":250,"category":228,"tags":251},"\u002Fposts\u002Fclaude-settings-codex-config","AI 相關紀錄 v4｜Claude Code settings \u002F Codex config 基本設定","整理 Claude Code settings.json 與 Codex config.toml 的設定層級、權限控制和常見基本設定。",[230,231,232,252,253],"settings.json","config.toml",{"path":255,"title":256,"description":257,"category":228,"tags":258},"\u002Fposts\u002Fclaude-codex-rules-structure","AI 相關紀錄 v5｜Rules：專案規則多了之後怎麼拆？","整理 Claude Code Rules 與 Codex AGENTS.md 的拆分方式，說明何時該拆、怎麼依目錄管理專案規則。",[230,231,232,259,235],"Rules",{"path":261,"title":262,"description":263,"category":228,"tags":264},"\u002Fposts\u002Fclaude-codex-slash-commands","AI 相關紀錄 v6｜Commands \u002F Slash Commands：CLI 裡的 `\u002F` 指令是什麼？","介紹 Claude Code 與 Codex CLI 的 Slash Commands，整理常用內建指令、自訂指令與 Skills 的差異。",[230,231,232,265],"Slash Commands",{"path":267,"title":268,"description":269,"category":228,"tags":270},"\u002Fposts\u002Fclaude-codex-skills","AI 相關紀錄 v7｜Skills：把重複工作流程整理起來","介紹 Claude Code 與 Codex Skills，整理適合保存成 Skill 的重複流程、基本結構與使用方式。",[230,231,232,271],"Skills",{"path":273,"title":274,"description":275,"category":228,"tags":276},"\u002Fposts\u002Fclaude-codex-agents-subagents","AI 相關紀錄 v8｜Agent \u002F Subagent：什麼時候真的需要分工？","整理 Agent、Subagent 與 Custom Agent 的用途，說明何時適合分工，以及它們和 Rules、Skills 的差異。",[230,231,232,277,278],"Agent","Subagent",{"path":280,"title":281,"description":282,"category":228,"tags":283},"\u002Fposts\u002Fmcp-basics","AI 相關紀錄 v9｜MCP：讓 AI 使用其他工具與資料","介紹 MCP 如何讓 AI 使用外部工具與資料，並以 Pencil MCP 說明實際用途、權限風險及與 Skill 的差異。",[230,284,231,232,285],"MCP","Pencil",{"path":287,"title":288,"description":289,"category":228,"tags":290},"\u002Fposts\u002Fai-coding-agent-concepts-summary","AI 相關紀錄 v10｜基本概念小結論","用一篇快速整理 CLAUDE.md、AGENTS.md、設定檔、Rules、Commands、Skills、Agent 與 MCP 的角色和差異。",[230,231,232,284,271,277],{"path":292,"title":293,"description":294,"category":228,"tags":295},"\u002Fposts\u002Fclaude-code-codex-model-selection","Claude Code 與 Codex：不同模型怎麼選？","比較 Claude Code 與 Codex 不同模型的速度、能力與成本取捨，依工作難度整理實用的選擇方向。",[230,231,296,297],"Codex","模型選擇",{"path":299,"title":300,"description":301,"category":228,"tags":302},"\u002Fposts\u002Fclaude-model-selection","Claude 模型簡單怎麼選？","整理 Claude 各模型在速度、能力與使用情境上的差異，提供從輕量工作到複雜任務的選擇方向。",[230,231,303,297],"Claude",{"path":305,"title":306,"description":307,"category":228,"tags":308},"\u002Fposts\u002Fcodex-model-selection","Codex 模型簡單怎麼選？","整理 Codex 各模型在速度、能力與使用情境上的差異，提供從簡單修改到大型端到端任務的選擇方向。",[230,296,309,297],"OpenAI",{"path":311,"title":312,"description":313,"category":228,"tags":314},"\u002Fposts\u002Fclaude-code-codex-cli-command-cheatsheet","Claude Code \u002F Codex CLI 常用指令速查表","整理 Claude Code 與 Codex CLI 的常用斜線指令、快捷操作與進階功能，方便需要時快速查找。",[230,231,232,265,315],"速查表",{"id":317,"title":197,"body":318,"category":16,"description":198,"draft":670,"extension":671,"image":672,"meta":673,"navigation":674,"path":196,"publishedAt":675,"relatedExperiments":676,"seo":677,"stem":678,"tags":679,"updatedAt":675,"__hash__":680},"posts\u002Fposts\u002F20260724.ios-iframe-google-login-blank-page.md",{"type":319,"value":320,"toc":658},"minimark",[321,329,332,335,338,341,345,348,358,361,367,370,373,376,379,385,388,391,397,400,403,411,415,418,424,427,430,436,439,442,449,453,456,459,465,468,472,475,478,484,487,493,496,503,506,510,517,520,550,553,556,559,562,581,584,587,590,595,598,605,608,611,617,620,623,638,641,644,647,654],[322,323,324,325,328],"p",{},"這次遇到的問題，發生在一個透過 ",[326,327,201],"code",{}," 嵌入的 Web 應用中。",[322,330,331],{},"使用者會先從宿主頁面開啟 iframe，再從 iframe 內點擊 Google 第三方登入。",[322,333,334],{},"大部分裝置都能正常登入，但部分較新 iOS 版本的裝置在選擇 Google 帳號後，登入流程會中斷，甚至出現空白頁，最後無法正常完成登入。",[322,336,337],{},"麻煩的是，這個問題並不是所有 iPhone 都能穩定重現。",[322,339,340],{},"當時陸續排查過 Google 帳號、Cookie、ITP、CSP、API、iframe 權限等方向，最後透過前端診斷紀錄與不同裝置的對照測試，才找到真正影響流程的原因。",[342,343,344],"h2",{"id":344},"當時的登入架構",[322,346,347],{},"整體流程可以簡化成：",[349,350,356],"pre",{"className":351,"code":353,"language":354,"meta":355},[352],"language-text","原本A頁面\n   ↓\n開啟 iframe\n   ↓\n使用者在 iframe 內點擊 Google 登入\n   ↓\n另外開啟 Google 登入分頁\n   ↓\nA頁面與 iframe 進入背景\n   ↓\n使用者選擇 Google 帳號\n   ↓\nGoogle 完成驗證後關閉分頁\n   ↓\n回到原本A頁面登入成功畫面\n","text","",[326,357,353],{"__ignoreMap":355},[322,359,360],{},"這個流程有一個很重要的前提：",[362,363,364],"blockquote",{},[322,365,366],{},"原本等待 Google 登入結果的頁面必須還存在。",[322,368,369],{},"但到了部分 iOS 裝置，問題就出現在這裡。",[342,371,372],{"id":372},"問題出在背景頁面遭到回收",[322,374,375],{},"Google 登入分頁開啟之後，原本的宿主A頁面與 iframe 會退到背景。",[322,377,378],{},"正常情況下，iOS 該頁面應該會進行等待確認 google 是否已登入的動作：",[349,380,383],{"className":381,"code":382,"language":354,"meta":355},[352],"宿主A頁面進入背景\n   ↓\n進行等待確認 google 是否已登入動作\n   ↓\n頁面仍然存在\n   ↓\n回到頁面\n   ↓\n接收到google已登入流程\n   ↓\n登入流程繼續並完成\n",[326,384,382],{"__ignoreMap":355},[322,386,387],{},"但在發生問題的裝置上，實際觀察到的是背景頁面遭到系統回收。",[322,389,390],{},"等使用者完成 Google 登入再回來時：",[349,392,395],{"className":393,"code":394,"language":354,"meta":355},[352],"Google 登入分頁開啟\n   ↓\n宿主A頁面進入背景\n   ↓\niOS 回收背景頁面\n   ↓\n使用者回到原頁面\n   ↓\n頁面重新載入\n   ↓\niframe 重新建立\n   ↓\n原本的 頁面、callback 與暫存狀態消失\n",[326,396,394],{"__ignoreMap":355},[322,398,399],{},"因此真正造成問題的不是單純「背景頁面被暫停」。",[322,401,402],{},"而是：",[362,404,405],{},[322,406,407],{},[408,409,410],"strong",{},"頁面遭到回收後發生 Reload，原本等待 Google 登入結果的 JavaScript 執行環境已經不存在。",[342,412,414],{"id":413},"為什麼-popup-登入會受到影響","為什麼 Popup 登入會受到影響？",[322,416,417],{},"Popup 類型的登入流程，可以簡化成：",[349,419,422],{"className":420,"code":421,"language":354,"meta":355},[352],"iframe 內的 Web 應用\n   ↓\n開啟 Google 登入分頁\n   ↓\nGoogle 完成驗證\n   ↓\n把登入結果交回原本的登入流程\n",[326,423,421],{"__ignoreMap":355},[322,425,426],{},"只要原頁面還活著，流程就能繼續。",[322,428,429],{},"但如果 Google 登入期間原頁面遭到 iOS 回收：",[349,431,434],{"className":432,"code":433,"language":354,"meta":355},[352],"Google 完成登入\n   ↓\n準備回傳登入結果\n   ↓\n原頁面已經 Reload\n   ↓\n原本的 callback 不存在\n   ↓\nPopup 登入流程無法接續導致一片空白\n   ↓\n手動切回A頁面反而重整登入失敗\n",[326,435,433],{"__ignoreMap":355},[322,437,438],{},"這也讓問題一開始很難從 API 或 Server Log 找到。",[322,440,441],{},"因為真正出問題的時候，不一定是 Google 回傳了一個錯誤，而可能是：",[362,443,444],{},[322,445,446],{},[408,447,448],{},"原本應該接收登入結果的頁面已經被重新載入。",[342,450,452],{"id":451},"最後的處理方式依-ios-版本分流","最後的處理方式：依 iOS 版本分流",[322,454,455],{},"最後並沒有把所有裝置全部改成 Redirect，而是依裝置與 iOS 版本進行分流。",[322,457,458],{},"概念大致如下：",[349,460,463],{"className":461,"code":462,"language":354,"meta":355},[352],"Google Login\n   ↓\n判斷裝置與 iOS 版本 (IOS26以上走 Redirect, IOS26以下走舊有流程)\n   ↓\n較新的 iOS\n   └─ Redirect 登入\n\n其他裝置 \u002F 舊版 iOS\n   └─ 維持原本 Popup 登入\n",[326,464,462],{"__ignoreMap":355},[322,466,467],{},"原本能正常使用 Popup 的環境繼續維持既有機制，而容易受到背景頁面回收影響的新版 iOS，則改走 Redirect。",[342,469,471],{"id":470},"redirect-後還要能接回登入流程","Redirect 後還要能接回登入流程",[322,473,474],{},"單純改成 Redirect 還不夠。",[322,476,477],{},"因為頁面仍然可能在登入期間被 iOS 回收，所以在離開頁面之前，需要先保存一個能辨識「這一次登入流程」的資訊，例如：",[349,479,482],{"className":480,"code":481,"language":354,"meta":355},[352],"loginKey\nstate\ntransactionId\n",[326,483,481],{"__ignoreMap":355},[322,485,486],{},"流程就變成：",[349,488,491],{"className":489,"code":490,"language":354,"meta":355},[352],"iframe 內開始 Google 登入\n   ↓\n先保存 loginKey \u002F state\n   ↓\n前往 Google Login\n   ↓\nGoogle 完成驗證\n   ↓\nRedirect 回系統\n   ↓\n原頁面如果已被回收就重新載入\n   ↓\n讀取之前保存的 loginKey\n   ↓\n向 Server 確認登入結果\n   ↓\n重新接回登入狀態\n",[326,492,490],{"__ignoreMap":355},[322,494,495],{},"最大的差別在於：",[362,497,498],{},[322,499,500],{},[408,501,502],{},"頁面 Reload 不再等於登入流程直接失敗。",[322,504,505],{},"就算原本的 JavaScript 資料已經不存在，只要還保留這一次登入流程的識別資訊，就有機會重新向 Server 接回登入結果。",[342,507,509],{"id":508},"不要直接把-google-token-存進-localstorage","不要直接把 Google Token 存進 localStorage",[322,511,512,513,516],{},"這裡的「保存登入資訊」並不是指把 Google Access Token 或 ID Token 長時間放進 ",[326,514,515],{},"localStorage","。",[322,518,519],{},"比較適合保存的是短效、不能直接代表登入身分的識別值，例如：",[349,521,525],{"className":522,"code":523,"language":524,"meta":355,"style":355},"language-js shiki shiki-themes github-light github-dark-default","localStorage.setItem(\"googleLoginState\", loginKey);\n","js",[326,526,527],{"__ignoreMap":355},[528,529,532,536,540,543,547],"span",{"class":530,"line":531},"line",1,[528,533,535],{"class":534},"szmH1","localStorage.",[528,537,539],{"class":538},"sVjZL","setItem",[528,541,542],{"class":534},"(",[528,544,546],{"class":545},"sNbzA","\"googleLoginState\"",[528,548,549],{"class":534},", loginKey);\n",[322,551,552],{},"頁面重新載入後，再由這個識別值向 Server 查詢這次登入是否完成。",[322,554,555],{},"這樣保存的是「我要接回哪一次登入流程」，而不是直接把真正的登入憑證留在瀏覽器中。",[342,557,558],{"id":558},"降低記憶體只能治標",[322,560,561],{},"另外一個可以做的方向，是在進行第三方登入前暫停一些比較耗資源的內容，例如：",[563,564,565,569,572,575,578],"ul",{},[566,567,568],"li",{},"WebGL \u002F Canvas",[566,570,571],{},"大型動畫",[566,573,574],{},"影片",[566,576,577],{},"高頻 Timer",[566,579,580],{},"不必要的背景工作",[322,582,583],{},"這些作法有機會降低背景頁面的記憶體壓力。",[322,585,586],{},"但它只能降低頁面遭到回收的機率，不能保證 iOS 一定不會回收背景頁面。",[322,588,589],{},"因此與其把設計建立在：",[362,591,592],{},[322,593,594],{},"頁面一定不能被 Reload。",[322,596,597],{},"更可靠的方向應該是：",[362,599,600],{},[322,601,602],{},[408,603,604],{},"就算頁面被 Reload，重要流程仍然能夠恢復。",[342,606,607],{"id":607},"這次踩坑後的心得",[322,609,610],{},"桌面瀏覽器上很常見的第三方登入流程：",[349,612,615],{"className":613,"code":614,"language":354,"meta":355},[352],"開 Popup\n→ 等 callback\n→ 取得登入結果\n→ 完成登入\n",[326,616,614],{"__ignoreMap":355},[322,618,619],{},"到了行動裝置，不一定能假設原本的 JavaScript Context 會從流程開始一路存在到結束。",[322,621,622],{},"尤其當流程包含：",[563,624,625,627,630,633,636],{},[566,626,201],{},[566,628,629],{},"第三方 OAuth",[566,631,632],{},"開啟新分頁",[566,634,635],{},"頁面進入背景",[566,637,206],{},[322,639,640],{},"重要流程最好具備可以重新接回的機制。",[322,642,643],{},"這次最後真正解決的不只是「Google 登入空白頁」這個問題。",[322,645,646],{},"更重要的是重新認識：",[362,648,649],{},[322,650,651],{},[408,652,653],{},"不要假設頁面不會消失，而是讓流程在頁面被重新載入後，仍然有辦法接著走下去。",[655,656,657],"style",{},"html pre.shiki code .szmH1, html code.shiki .szmH1{--shiki-default:#24292E;--shiki-dark:#E6EDF3}html pre.shiki code .sVjZL, html code.shiki .sVjZL{--shiki-default:#6F42C1;--shiki-dark:#D2A8FF}html pre.shiki code .sNbzA, html code.shiki .sNbzA{--shiki-default:#032F62;--shiki-dark:#A5D6FF}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}",{"title":355,"searchDepth":659,"depth":659,"links":660},3,[661,663,664,665,666,667,668,669],{"id":344,"depth":662,"text":344},2,{"id":372,"depth":662,"text":372},{"id":413,"depth":662,"text":414},{"id":451,"depth":662,"text":452},{"id":470,"depth":662,"text":471},{"id":508,"depth":662,"text":509},{"id":558,"depth":662,"text":558},{"id":607,"depth":662,"text":607},false,"md",null,{},true,"2026-07-24",[],{"title":197,"description":198},"posts\u002F20260724.ios-iframe-google-login-blank-page",[73,200,201,202,203,204,205,206],"bq0pLcL6RTwq6PtDZ0JoUINT7bdO946D96iD3-Q6lz4",[682,685],{"title":209,"path":208,"stem":683,"description":210,"category":16,"publishedAt":684,"children":-1},"posts\u002F20260725.ios-login-tab-return-behavior","2026-07-25",{"title":190,"path":189,"stem":686,"description":191,"category":16,"publishedAt":687,"children":-1},"posts\u002F20260629.nuxt-route-rules-redirect","2026-06-29",1791786900950]