This bug has already been fixed by Zapstore. Please update Zapstore to the latest version, then go to Zapstore’s settings and select “Delete local cache.”