Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

iCloud document folder does not exists #60

Open
philipparndt opened this issue May 26, 2020 · 7 comments
Open

iCloud document folder does not exists #60

philipparndt opened this issue May 26, 2020 · 7 comments
Milestone

Comments

@philipparndt
Copy link
Owner

see comments on #55

@philipparndt
Copy link
Owner Author

philipparndt commented May 26, 2020

Hi @AndreCouture @RoSchmi

still some pending todos but I implemented a draft with a document picker in the branch https://github.com/philipparndt/mqtt-analyzer/tree/document-picker

With the document picker it should be now possible to import files (currently all kind of files filtering is missing) to the local storage.

image

image

Pending TODOs:

  • filtering for certificate files (done ✅)
  • improve refresh handling (currently manual refresh necessary) (done ✅)
  • tests

@AndreCouture
Copy link

AndreCouture commented May 27, 2020 via email

@philipparndt
Copy link
Owner Author

philipparndt commented May 28, 2020

The Import from iCloud... button should be visible when Local is selected in the picker. This is also the new default when creating a new setting. Did you checked out the document-picker branch? This is currently not merged on master.

@AndreCouture
Copy link

AndreCouture commented May 28, 2020 via email

@philipparndt
Copy link
Owner Author

philipparndt commented May 29, 2020

I downloaded from the link you provided.

The TestFlight build currently do not have this change as it requires an Apple review to be deployed. I can add you to the list of internal tester when you like be on that list. With that you can get TestFlight builds right after they are pushed to app store connect (after some automated validations)

Can you add a version number in the about to see exactly which build it is running?

Added this: #61

The version number should be 1.7.0.53

@AndreCouture
Copy link

AndreCouture commented May 29, 2020 via email

@RoSchmi
Copy link

RoSchmi commented May 29, 2020

Great. Just pulled the last master branch from Github. Browsing and picking Certificate worked as well.

@philipparndt philipparndt added this to the 1.7 milestone Jun 3, 2020
@philipparndt philipparndt modified the milestones: 1.7, 2.x Apr 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants