Skip to content

Library publishing restriction info #270

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

Merged
merged 9 commits into from
Feb 11, 2025

Conversation

pinkeshmars
Copy link
Collaborator

@pinkeshmars pinkeshmars commented Jan 31, 2025

Description

Library publishing restriction info

Linear ticket and magic word Fixes DEVR-719, Fixes DEVR-798

Type of change

  • Typo fix
  • New feature
  • Enhancement to current docs
  • Removed outdated references
  • Update assets

@pinkeshmars pinkeshmars requested a review from PoojaB26 January 31, 2025 07:04
Copy link

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

Copy link
Collaborator

@PoojaB26 PoojaB26 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Need clarifications about the points missed. lmk if its added somewhere else, but ideally it should be the same place.

@@ -80,6 +80,10 @@ To publish a FlutterFlow project as a library, start by creating a FlutterFlow p
- It's recommended to include a message that tells users what has changed in the version your are publishing.
:::

:::warning
You cannot publish a project as a library if it has already been deployed to the Google Play Store or the Apple App Store. Additionally, the Publish button is disabled if a deployment process has started and failed.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @pinkeshmars what about the other points Sameer mentioned?

✅ No errors or warnings

✅ Main Branch

✅ Pro Plan

✅ Not cloned from a MarketPlace Project

:::warning
You cannot publish a project as a Library if it has already been deployed to the Google Play Store or the Apple App Store. Additionally, the Publish button is disabled if a deployment process was started and failed.

To publish a project as a library, ensure that:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we not combine all the points in a single bullet list?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done!

@pinkeshmars
Copy link
Collaborator Author

@PoojaB26 could you please take a look again?

@pinkeshmars pinkeshmars merged commit 95a2e54 into main Feb 11, 2025
1 check passed
@PoojaB26 PoojaB26 deleted the fix/library-publish-button-status branch February 11, 2025 14:01
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

Successfully merging this pull request may close these issues.

2 participants