This repository has been archived by the owner on Jan 7, 2020. It is now read-only.

Trying to access another app's own container after logging with `loginForTest` triggers an error #259

Open

bochaco opened this issue Aug 7, 2018 · 0 comments

Labels

Contributor

bochaco commented Aug 7, 2018 •

edited

Loading

Trying to access another app's own container after loging with loginForTest triggers an error stating the container doesn't exist. For a detailed discussions look at this thread: https://forum.safedev.org/t/loginfortest-with-two-apps/1752/4

This seems to be an issue in the safe_app lib reported with: https://github.com/maidsafe/safe_client_libs/issues/710

This can be also reproduced using the test created in PR #254

The text was updated successfully, but these errors were encountered:

bochaco added this to the v0.9.1 milestone

bochaco added the bug label

bochaco modified the milestones: v0.9.1, v0.9.2

bochaco removed this from the v0.10.0 milestone

bochaco added the blocked label

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.