Describe the bug
While using at_client: "3.0.20" on atmospherePro, I could not see any received files.
when looked into getAtKeys method, it was giving no data .
atClient.getAtKeys( regex: 'file_transfer_' );
var scanResult = await getSecondary().executeVerb(builder);
Similarly, to populate sent history we also use getAtKeys method which is working as expected.
Only difference we have is sharedBy paramater is added.
use atmospherePro trunk branch and update dependency
check if you are on at_client : "3.0.20"
go to received files, data should not show up.
Expected behavior
atClient.getAtKeys should return the atKeys matching the regex.
Screenshots
Smartphone (please complete the following information):
macOS
Were you using an @application when the bug was found?
atmospherePro
Additional context
If we use the same atsign on testflight version or point to at_client: "3.0.18" it works as expected and we could see received files.
Describe the bug While using at_client: "3.0.20" on atmospherePro, I could not see any received files. when looked into getAtKeys method, it was giving no data .
atClient.getAtKeys( regex: 'file_transfer_' );
var scanResult = await getSecondary().executeVerb(builder);
Similarly, to populate sent history we also use getAtKeys method which is working as expected. Only difference we have is sharedBy paramater is added.
atClient.getAtKeys( regex: MixedConstants.FILE_TRANSFER_KEY, sharedBy: atClient.getCurrentAtSign() );
To Reproduce Steps to reproduce the behavior:
Expected behavior atClient.getAtKeys should return the atKeys matching the regex.
Screenshots
Smartphone (please complete the following information):
Were you using an @application when the bug was found?
Additional context If we use the same atsign on testflight version or point to at_client: "3.0.18" it works as expected and we could see received files.