Lee•4mo ago

안드로이드 웹뷰에서 결제창 호출 시 웹뷰 충돌

안녕하세요. 현재 웹뷰에서 결제창을 호출하면 웹뷰 충돌이 나서 앱이 죽어버립니다. 문제는 죽어버릴때도 있고 정상적으로 호출될때도 있고 그렇네요.. 결제창에서 결제 UI렌더링 하는 부분(renderPaymentMethods 호출과정)에서 문제가 생기는거 같습니다. 웹은 정상적으로 호출이 되구요. 앱쪽 소스는 https://docs.tosspayments.com/guides/v2/webview 여기 나와있는대로 구현했습니다. 오류 내역입니다.

10-28 16:38:22.440 12193 12193 E chromium: [1028/163822.439953:ERROR:file_io_posix.cc(144)] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq: Permission denied (13)
10-28 16:38:22.440 12193 12193 E chromium: [1028/163822.440675:ERROR:ptrace_client.cc(363)] Broker Open: access denied
10-28 16:38:22.542 12193 12193 F crashpad: -----BEGIN CRASHPAD MINIDUMP----
10-28 16:38:22.572 12193 12193 F crashpad: )iyJn(ecQo,x`--u3RY[}M+k_k@~!P)W}
10-28 16:38:22.572 12193 12193 F crashpad: wSrigF+LmQz~{uB*TC=7@1/,|,8\4$8j+
...
10-28 16:38:22.582 12193 12193 F crashpad: -----END CRASHPAD MINIDUMP-----
10-28 16:38:22.994 11827 11827 E chromium: [ERROR:aw_browser_terminator.cc(156)] Renderer process (11911) crash detected (code 5).
10-28 16:38:22.996 11827 11827 F chromium: [FATAL:crashpad_client_linux.cc(732)] Render process (11911)'s crash wasn't handled by all associated  webviews, triggering application crash.

10-28 16:38:22.440 12193 12193 E chromium: [1028/163822.439953:ERROR:file_io_posix.cc(144)] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq: Permission denied (13)
10-28 16:38:22.440 12193 12193 E chromium: [1028/163822.440675:ERROR:ptrace_client.cc(363)] Broker Open: access denied
10-28 16:38:22.542 12193 12193 F crashpad: -----BEGIN CRASHPAD MINIDUMP----
10-28 16:38:22.572 12193 12193 F crashpad: )iyJn(ecQo,x`--u3RY[}M+k_k@~!P)W}
10-28 16:38:22.572 12193 12193 F crashpad: wSrigF+LmQz~{uB*TC=7@1/,|,8\4$8j+
...
10-28 16:38:22.582 12193 12193 F crashpad: -----END CRASHPAD MINIDUMP-----
10-28 16:38:22.994 11827 11827 E chromium: [ERROR:aw_browser_terminator.cc(156)] Renderer process (11911) crash detected (code 5).
10-28 16:38:22.996 11827 11827 F chromium: [FATAL:crashpad_client_linux.cc(732)] Render process (11911)'s crash wasn't handled by all associated  webviews, triggering application crash.