# Error: Only the original thread that created a view hierarchy can touch its views **URL:** \ **Category:** Technical\ **Created:** [December 10, 2018, 9:54pm UTC](https://community.blockcerts.org/t/error-only-the-original-thread-that-created-a-view-hierarchy-can-touch-its-views/1565 "2018-12-10T21:54:00Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![mlisle](https://sea2.discourse-cdn.com/flex016/user_avatar/community.blockcerts.org/mlisle/32/454_2.png) [@mlisle](https://community.blockcerts.org/u/mlisle)\ **Post date:** [December 10, 2018, 9:54pm UTC](https://community.blockcerts.org/t/error-only-the-original-thread-that-created-a-view-hierarchy-can-touch-its-views/1565/1 "2018-12-10T21:54:01Z")
Hi everyone, Reposting from [https://github.com/blockchain-certificates/wallet-android/issues/25](https://github.com/blockchain-certificates/wallet-android/issues/25) One of our users is receiving an error when attempting to add us as an issuer to his Blockcerts wallet (Android). After entering our issuer URL, entering his one-time code, and tapping “Add Issuer,” he gets: “Only the original thread that created a view hierarchy can touch its views.” He has tried multiple times, over multiple days, and gets this error each time. Other users have been able to add us as an issuer with no errors during this same time frame. Does this error ring any bells for anyone? ---
**Author:** ![aronning](https://avatars.discourse-cdn.com/v4/letter/a/47e85d/32.png) [@aronning](https://community.blockcerts.org/u/aronning)\ **Post date:** [December 12, 2018, 3:51pm UTC](https://community.blockcerts.org/t/error-only-the-original-thread-that-created-a-view-hierarchy-can-touch-its-views/1565/2 "2018-12-12T15:51:40Z")
Very weird. Sounds like it could be an android version / model bug going on. Haven’t seen that one myself. Do you have any device information? ---
**Author:** ![mlisle](https://sea2.discourse-cdn.com/flex016/user_avatar/community.blockcerts.org/mlisle/32/454_2.png) [@mlisle](https://community.blockcerts.org/u/mlisle)\ **Post date:** [December 14, 2018, 3:25pm UTC](https://community.blockcerts.org/t/error-only-the-original-thread-that-created-a-view-hierarchy-can-touch-its-views/1565/3 "2018-12-14T15:25:12Z")
He reports that he’s using Pixel 2, Android version 9. ---
**Author:** ![mlisle](https://sea2.discourse-cdn.com/flex016/user_avatar/community.blockcerts.org/mlisle/32/454_2.png) [@mlisle](https://community.blockcerts.org/u/mlisle)\ **Post date:** [February 7, 2019, 7:54pm UTC](https://community.blockcerts.org/t/error-only-the-original-thread-that-created-a-view-hierarchy-can-touch-its-views/1565/4 "2019-02-07T19:54:21Z")
FYI… I just received the same report from a user on a OnePlus 5 running Android 9. Perhaps this is an issue with Android 9? ---
**Author:** ![aronning](https://avatars.discourse-cdn.com/v4/letter/a/47e85d/32.png) [@aronning](https://community.blockcerts.org/u/aronning)\ **Post date:** [February 8, 2019, 4:22pm UTC](https://community.blockcerts.org/t/error-only-the-original-thread-that-created-a-view-hierarchy-can-touch-its-views/1565/5 "2019-02-08T16:22:34Z")
I know other users with Android 9 do not have this problem and I haven’t seen/heard of this error myself. Could be a bit more specific than just Android 9. Could you provide a bit more information on this error? How does it appear - does it show in the logs or it is visually displayed back to the user? Does the whole app crash afterwards? ---
**Author:** ![aronning](https://avatars.discourse-cdn.com/v4/letter/a/47e85d/32.png) [@aronning](https://community.blockcerts.org/u/aronning)\ **Post date:** [February 8, 2019, 4:36pm UTC](https://community.blockcerts.org/t/error-only-the-original-thread-that-created-a-view-hierarchy-can-touch-its-views/1565/6 "2019-02-08T16:36:12Z")
Wow, as soon as I say that, I reproduced the error on my android phone (Nexus v7) when I put in some garbage values like “[https://test.com](https://test.com)” for the issuer and “t” for the token. I emailed the logs to myself so I’ll try to take a look at it. Edit: even reproduced it by using good values