After first run, app requests permission, after accept permission show up internal loading. After restart app all ok.

Try disable permission and run app.

First of all, great work on this repository. I'm starting to learn dart/flutter but your project is quite close to what I'm planning to build so it's really helpful in learning.

I've just tried to clone your code and run it on Ubuntu 22.04 with the following version

$ flutter --version
Flutter 3.0.5 • channel stable • https://github.com/flutter/flutter.git
Framework • revision f1875d570e (4 weeks ago) • 2022-07-13 11:24:16 -0700
Engine • revision e85ea0e79c
Tools • Dart 2.17.6 • DevTools 2.12.2

However, when running flutter run -d chrome or flutter run -d linux i'm getting the following exception:

The following UnsupportedError was thrown building Consumer<AppProvider>(dirty, dependencies:
[_InheritedProviderScope<AppProvider?>]):
Unsupported operation: Platform._operatingSystem

The relevant error-causing widget was:
  Consumer<AppProvider> Consumer:file:///home/user/projects/project/lib/app.dart:13:12

When the exception was thrown, this was the stack:
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 251:49     throw_
dart-sdk/lib/_internal/js_dev_runtime/patch/io_patch.dart 244:5                  _operatingSystem
dart-sdk/lib/io/platform_impl.dart 56:40                                         get operatingSystem
dart-sdk/lib/io/platform.dart 64:45                                              get _operatingSystem
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/operations.dart 839:8  get
dart-sdk/lib/io/platform.dart 153:47                                             get isIOS
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/operations.dart 839:8  get
packages/filex/app.dart 22:26                                                    <fn>
...
Another exception was thrown: Unsupported operation: Platform._operatingSystem

According to your Readme it's supposed to work on my machine. Any chance you could point at things to check?

Any help really appreciated :)

Hey, I'm trying to execute this project locally for web or desktop but it's one-step-at-a-time problem fixing. I'm a Flutter noob so it's likely I'm something doing wrong but thought that just in case I'd ask whether FileX is intended and was tested to run on chrome and linux devices?

Update: I've just installed Android Studio and got it working with flutter. Seems that the same project is working fine there.

I am clone the code and create debug build than first time when I give access permission than showing loader and app stuck after app killed and again open it's works perfectly .

Automated style fixes for #20, created by Restyled.

The following restylers made fixes:

• prettier-yaml
• whitespace

To incorporate these changes, merge this Pull Request into the original. We recommend using the Squash or Rebase strategies.

NOTE: As work continues on the original Pull Request, this process will re-run and update (force-push) this Pull Request with updated style fixes as necessary. If the style is fixed manually at any point (i.e. this process finds no fixes to make), this Pull Request will be closed automatically.

Sorry if this was unexpected. To disable it, see our documentation.

Automated style fixes for #15, created by Restyled.

The following restylers made fixes:

• prettier-yaml

To incorporate these changes, merge this Pull Request into the original. We recommend using the Squash or Rebase strategies.

NOTE: As work continues on the original Pull Request, this process will re-run and update (force-push) this Pull Request with updated style fixes as necessary. If the style is fixed manually at any point (i.e. this process finds no fixes to make), this Pull Request will be closed automatically.

Sorry if this was unexpected. To disable it, see our documentation.

Beep boop. Your images are optimized!

Your image file size has been reduced by 6% 🎉

Black Lives Matter | 💰 donate | 🎓 learn | ✍🏾 sign

📝 docs | :octocat: repo | 🙋🏾 issues | 🏅 swag | 🏪 marketplace

Automated style fixes for #9, created by Restyled.

The following restylers made fixes:

• whitespace

To incorporate these changes, merge this Pull Request into the original. We recommend using the Squash or Rebase strategies.

NOTE: As work continues on the original Pull Request, this process will re-run and update (force-push) this Pull Request with updated style fixes as necessary. If the style is fixed manually at any point (i.e. this process finds no fixes to make), this Pull Request will be closed automatically.

Sorry if this was unexpected. To disable it, see our documentation.

Automated style fixes for #7, created by Restyled.

The following restylers made fixes:

• whitespace

To incorporate these changes, merge this Pull Request into the original. We recommend using the Squash or Rebase strategies.

NOTE: As work continues on the original Pull Request, this process will re-run and update (force-push) this Pull Request with updated style fixes as necessary. If the style is fixed manually at any point (i.e. this process finds no fixes to make), this Pull Request will be closed automatically.

Sorry if this was unexpected. To disable it, see our documentation.

Automated style fixes for #4, created by Restyled.

The following restylers made fixes:

• prettier-markdown

To incorporate these changes, merge this Pull Request into the original. We recommend using the Squash or Rebase strategies.

NOTE: As work continues on the original Pull Request, this process will re-run and update (force-push) this Pull Request with updated style fixes as necessary. If the style is fixed manually at any point (i.e. this process finds no fixes to make), this Pull Request will be closed automatically.

Sorry if this was unexpected. To disable it, see our documentation.

Automated style fixes for #4, created by Restyled.

The following restylers made fixes:

• prettier-yaml
• whitespace

To incorporate these changes, merge this Pull Request into the original. We recommend using the Squash or Rebase strategies.

NOTE: As work continues on the original Pull Request, this process will re-run and update (force-push) this Pull Request with updated style fixes as necessary. If the style is fixed manually at any point (i.e. this process finds no fixes to make), this Pull Request will be closed automatically.

Sorry if this was unexpected. To disable it, see our documentation.