SOLIDPOD: Revoke permission of previously shared folder removes owner's access to the folder

Describe the Bug

Revoke the permission of a previously shared folder will change the ACL of the folder such that the owner can no longer access it.

To Reproduce

Steps to reproduce the behavior:

1. Use the example app of the current dev branch
2. Login with WEBID1 and WEBID2, respectively. This is to initialise the default folder structure.
3. Login with WEBID1, click Create Resource with ACL Inheritance, set resource path to dir1/dir2/file1.ttl and parent directory to dir1/, click Create resource.
4. Go to home page, click Read Resource with ACL Inheritance, set resource path to dir1/dir2/file1.ttl, and click read resource. The resource can be read without any problem.
5. Go to home page, click Add/Delete Permission from Any Resource, and grant Read access to dir1 to WEBID2.
6. Then on the same page, revoke that Read access.
7. Go to step 4, access resource dir1/dir2/file1.ttl leads to error Error reading file: Exception: Unknown error..
   ACL file contents are shown below.

dir1/.acl after step 3:

@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix : <#> .
@prefix acl: <http://www.w3.org/ns/auth/acl#> .
@prefix c0: <https://solid.dev.empwr.au/dc101/profile/card#> .

:Read
    a acl:Authorization ;
    acl:accessTo <./> ;
    acl:default <./> ;
    acl:agent c0:me ;
    acl:mode acl:Read .
:Write
    a acl:Authorization ;
    acl:accessTo <./> ;
    acl:default <./> ;
    acl:agent c0:me ;
    acl:mode acl:Write .
:Control
    a acl:Authorization ;
    acl:accessTo <./> ;
    acl:default <./> ;
    acl:agent c0:me ;
    acl:mode acl:Control .

dir1/.acl after step 5:

@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix : <#> .
@prefix acl: <http://www.w3.org/ns/auth/acl#> .
@prefix c0: <https://solid.dev.empwr.au/dc101/profile/card#> .
@prefix c1: <https://solid.dev.empwr.au/dc105/profile/card#> .

:Read
    a acl:Authorization ;
    acl:accessTo <./> ;
    acl:default <./> ;
    acl:agent c0:me, c1:me ;
    acl:mode acl:Read .
:Write
    a acl:Authorization ;
    acl:accessTo <./> ;
    acl:default <./> ;
    acl:agent c0:me ;
    acl:mode acl:Write .
:Control
    a acl:Authorization ;
    acl:accessTo <./> ;
    acl:default <./> ;
    acl:agent c0:me ;
    acl:mode acl:Control .

dir1/.acl after step 6:

@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix : <#> .
@prefix acl: <http://www.w3.org/ns/auth/acl#> .
@prefix c0: <https://solid.dev.empwr.au/dc101/profile/card#> .

:Read
    a acl:Authorization ;
    acl:accessTo <> ;
    acl:agent c0:me ;
    acl:mode acl:Read .
:Write
    a acl:Authorization ;
    acl:accessTo <> ;
    acl:agent c0:me ;
    acl:mode acl:Write .
:Control
    a acl:Authorization ;
    acl:accessTo <> ;
    acl:agent c0:me ;
    acl:mode acl:Control .

Expected Behaviour

Resource dir1/dir2/file1.ttl should be accessed without problems.

Context

Where has the issue been observed:

• Android
• Chrome
• iOS
• Linux
• macOS
• Web
• Windows