-
Notifications
You must be signed in to change notification settings - Fork 159
Dart package analysis fails on pub.dev, work locally #7644
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
Comments
Not entirely sure what is happening here, but it looks like you may be triggering the |
nodoc , that's warning right? that's result after run dartdoc, also success locally
|
When I download the latest archive of First, a bad reference from
Which is not a problem on
The root cause of these issues is that the package archive is not complete, references items outside of it. Your local setup may be different from what you are publishing, and the I'm unsure why we don't have the error in the |
@isoos Thanks, But our package should not have missing files. please help to check this case, facing same issue: pub.dev doc log: https://pub.dev/packages/zego_uikit_prebuilt_call/versions/4.8.2/score/log.txt my local test command: git clone https://github.com/ZEGOCLOUD/zego_uikit_prebuilt_call_flutter.git --depth 1
cd zego_uikit_prebuilt_call_flutter
dart pub global activate dartdoc 8.0.7
flutter --no-version-check pub global run dartdoc --output /tmp/dartdoc-zego_uikitQVAWHL --sanitize-html --max-file-count 10000000 --max-total-size 2147483648 --no-validate-links test result:
My dart version: $dart --version
Dart SDK version: 3.3.3 (stable) (Tue Mar 26 14:21:33 2024 +0000) on "macos_arm64" I also checked our repository and there is no |
I'm not sure about the other package, but the previous one has no |
Only if you have both files:
https://dart.dev/tools/pub/publishing#what-files-are-published |
👌🏻 |
I found that this problem has occurred before.
7521
7149
It is successful in my local area:

On pub.dev it is failed like this:
log
The text was updated successfully, but these errors were encountered: