[Galaxy Tab S Android Development] wbedard:
Hi [MENTION=2371134]Schischu[/MENTION], et al.

With the 12/05 update, I finally pulled the trigger on installing this ROM (I had been waiting until the 5GHz WiFi was sorted out...). I was aware of many users having difficulty with adding their account during the initial setup. With that in mind, my initial install followed the directions in the OP verbatim (FYI, I'm certainly not new to installing ROMS...) and I also got stuck at the point of adding my account during the Setup Wizard. After several more attempts using different versions of GApps and slight "shortcuts" in the workflow, nothing was getting past the Google Apps crash that many have reported.

At this point, I pulled a logcat to see what was going on. One thing that caught my eye in the logcat, around the time of the GApps crash was the following:

12-05 16:56:18.675 5435 5435 E AndroidRuntime: FATAL EXCEPTION: main
12-05 16:56:18.675 5435 5435 E AndroidRuntime: Process: com.google.android.gms.ui, PID: 5435
12-05 16:56:18.675 5435 5435 E AndroidRuntime: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.google.android.gms/com.google.android.gms.auth.accounts.minutemaid.MinuteMaidActivity}: android.util.AndroidRuntimeException: android.webkit.WebViewFactory$MissingWebViewPackageException: android.content.pm.PackageManager$NameNotFoundException: com.android.webview
12-05 16:56:18.675 5435 5435 E AndroidRuntime:	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2416)
12-05 16:56:18.675 5435 5435 E AndroidRuntime:	at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2476)
12-05 16:56:18.675 5435 5435 E AndroidRuntime:	at android.app.ActivityThread.-wrap11(ActivityThread.java)
12-05 16:56:18.675 5435 5435 E AndroidRuntime:	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1344)
12-05 16:56:18.675 5435 5435 E AndroidRuntime:	at android.os.Handler.dispatchMessage(Handler.java:102)
12-05 16:56:18.675 5435 5435 E AndroidRuntime:	at android.os.Looper.loop(Looper.java:148)
12-05 16:56:18.675 5435 5435 E AndroidRuntime:	at android.app.ActivityThread.main(ActivityThread.java:5417)
12-05 16:56:18.675 5435 5435 E AndroidRuntime:	at java.lang.reflect.Method.invoke(Native Method)
12-05 16:56:18.675 5435 5435 E AndroidRuntime:	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
12-05 16:56:18.675 5435 5435 E AndroidRuntime:	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
12-05 16:56:18.675 5435 5435 E AndroidRuntime: Caused by: android.util.AndroidRuntimeException: android.webkit.WebViewFactory$MissingWebViewPackageException: android.content.pm.PackageManager$NameNotFoundException: com.android.webview
12-05 16:56:18.675 5435 5435 E AndroidRuntime:	at android.webkit.WebViewFactory.getProviderClass(WebViewFactory.java:222)
12-05 16:56:18.675 5435 5435 E AndroidRuntime:	at android.webkit.WebViewFactory.getProvider(WebViewFactory.java:169)
12-05 16:56:18.675 5435 5435 E AndroidRuntime:	at android.webkit.CookieManager.getInstance(CookieManager.java:39)
12-05 16:56:18.675 5435 5435 E AndroidRuntime:	at com.google.android.gms.auth.accounts.a.<init>(SourceFile:37)
12-05 16:56:18.675 5435 5435 E AndroidRuntime:	at com.google.android.gms.auth.accounts.addaccount.a.a_(SourceFile:55)
12-05 16:56:18.675 5435 5435 E AndroidRuntime:	at com.google.android.gms.auth.accounts.minutemaid.g.a_(SourceFile:176)
12-05 16:56:18.675 5435 5435 E AndroidRuntime:	at android.support.v4.app.s.a(SourceFile:917)
12-05 16:56:18.675 5435 5435 E AndroidRuntime:	at android.support.v4.app.s.a(SourceFile:1138)
12-05 16:56:18.675 5435 5435 E AndroidRuntime:	at android.support.v4.app.a.run(SourceFile:740)
12-05 16:56:18.675 5435 5435 E AndroidRuntime:	at android.support.v4.app.s.i(SourceFile:1501)
12-05 16:56:18.675 5435 5435 E AndroidRuntime:	at android.support.v4.app.l.onStart(SourceFile:551)
12-05 16:56:18.675 5435 5435 E AndroidRuntime:	at android.app.Instrumentation.callActivityOnStart(Instrumentation.java:1237)
12-05 16:56:18.675 5435 5435 E AndroidRuntime:	at android.app.Activity.performStart(Activity.java:6253)
12-05 16:56:18.675 5435 5435 E AndroidRuntime:	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2379)
12-05 16:56:18.675 5435 5435 E AndroidRuntime:	... 9 more
12-05 16:56:18.675 5435 5435 E AndroidRuntime: Caused by: android.webkit.WebViewFactory$MissingWebViewPackageException: android.content.pm.PackageManager$NameNotFoundException: com.android.webview
12-05 16:56:18.675 5435 5435 E AndroidRuntime:	at android.webkit.WebViewFactory.fetchPackageInfo(WebViewFactory.java:120)
12-05 16:56:18.675 5435 5435 E AndroidRuntime:	at android.webkit.WebViewFactory.getProviderClass(WebViewFactory.java:194)
2-05 16:56:18.675 5435 5435 E AndroidRuntime:	... 22 more
12-05 16:56:18.675 5435 5435 E AndroidRuntime: Caused by: android.content.pm.PackageManager$NameNotFoundException: com.android.webview
12-05 16:56:18.675 5435 5435 E AndroidRuntime:	at android.app.ApplicationPackageManager.getPackageInfo(ApplicationPackageManager.java:137)
12-05 16:56:18.675 5435 5435 E AndroidRuntime:	at android.webkit.WebViewFactory.fetchPackageInfo(WebViewFactory.java:118)
12-05 16:56:18.675 5435 5435 E AndroidRuntime:	... 23 more

This suggested to me something seriously wrong with the Andoid WebView app, which most know as the replacement HTML viewer since Lollipop (IIRC...). Since I maintain a local backup of all my APKs, it was easy for me to try to address this with a quick "adb install ..." command. Without rebooting my device, I again tried to add my account and it immediately went to the normal interface for entering your email address without any prompt of Google Apps crashing. Wanting to know how "robust" this solution was, I rebooted my device without actually adding my account. After the reboot, I again tried to add my Google account and again, I got the normal interface and successfully added my account.

While I know not everyone keeps local copies of their APKs, I know most people in this thread should be able to pull a copy from their favorite (working) MM ROM or even APKMirror. Of course, I understand that some people, including Schischu won't require this workaround. However, since so many seem to be having this issue, I hope my "fix" allows you to finally use the ROM. I have been very excited since first reading about it and, I must say, it certainly seems to be every bit as wonderful as many have said. Thanks again Schischu for all your efforts with the project!

R/

wbedard