Skip to content

Update Mac AppStore Guide to support app names containing spaces#3923

Merged
leaanthony merged 3 commits into
wailsapp:masterfrom
cristianrgreco:patch-1
Nov 29, 2024
Merged

Update Mac AppStore Guide to support app names containing spaces#3923
leaanthony merged 3 commits into
wailsapp:masterfrom
cristianrgreco:patch-1

Conversation

@cristianrgreco

@cristianrgreco cristianrgreco commented Nov 28, 2024

Copy link
Copy Markdown
Contributor

Description

The script in the Mac App Store guide doesn't work for an app name containing spaces. This fix simply wraps arguments containing the app name in quotes.

Type of change

Please select the option that is relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration using wails doctor.

  • Windows
  • macOS
  • Linux

If you checked Linux, please specify the distro and version.

Test Configuration

Please paste the output of wails doctor. If you are unable to run this command, please describe your environment in as much detail as possible.

Checklist:

  • I have updated website/src/pages/changelog.mdx with details of this PR
  • My code follows the general coding style of this project
  • I have performed a self-review of my own code
  • [] I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes

Summary by CodeRabbit

  • New Features

    • Enhanced instructions for submitting Wails Apps to the Mac App Store, including detailed steps for certificates, identifiers, and provisioning profiles.
    • Introduced the ability to specify the minimum macOS version externally.
    • Added a feature to set the window class name on Windows.
  • Bug Fixes

    • Resolved cross-compilation issues with CGO.
    • Updated go-webview2 to fix a native webview2loader issue.
    • Corrected TypeScript definition for WindowSetSize.
  • Documentation

    • Improved clarity and flow of the Mac App Store submission guide.
    • Updated changelog to reflect various modifications and fixes, including support for application names with spaces.

@coderabbitai

coderabbitai Bot commented Nov 28, 2024

Copy link
Copy Markdown
Contributor

Walkthrough

The pull request includes updates to the documentation for submitting Wails Apps to the Mac App Store, enhancing clarity and precision in the instructions. Key modifications involve detailed steps for creating certificates, identifiers, and provisioning profiles. The document also clarifies the App Sandbox process and refines build and signing instructions. Additionally, the changelog has been updated to reflect various modifications, including bug fixes and new features, such as the ability to set the minimum macOS version externally and support for application names with spaces.

Changes

File Path Change Summary
website/docs/guides/mac-appstore.mdx Enhanced instructions for submitting Wails Apps, including details on certificates, provisioning profiles, App Sandbox, and build/signing processes. Improved readability and clarity throughout.
website/src/pages/changelog.mdx Updated changelog to reflect modifications, including removal of irrelevant references, bug fixes, and new features like setting the window class name and specifying the minimum macOS version.

Possibly related PRs

Suggested reviewers

  • leaanthony

🐰 "In the garden where bunnies play,
We’ve polished docs in a bright new way.
With clearer paths and steps to take,
Submitting apps, oh what a cake!
Hop along, let’s share the cheer,
Wails to the App Store, let’s make it clear!" 🐇


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@cristianrgreco cristianrgreco marked this pull request as ready for review November 28, 2024 17:52

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (3)
website/docs/guides/mac-appstore.mdx (1)

84-86: Consider enhancing the script with error handling and consistency

While the current changes fix the spaces issue, the script could benefit from additional improvements:

 #!/bin/bash
 
+# Exit on error
+set -e
+
 APP_CERTIFICATE="3rd Party Mac Developer Application: YOUR NAME (CODE)"
 PKG_CERTIFICATE="3rd Party Mac Developer Installer: YOUR NAME (CODE)"
 APP_NAME="YourApp"
 
+# Validate required variables
+if [ -z "$APP_NAME" ] || [ -z "$APP_CERTIFICATE" ] || [ -z "$PKG_CERTIFICATE" ]; then
+    echo "Error: Required variables not set"
+    exit 1
+fi
+
 wails build -platform darwin/universal -clean
 
-cp ./embedded.provisionprofile "./build/bin/$APP_NAME.app/Contents"
+cp "./embedded.provisionprofile" "./build/bin/$APP_NAME.app/Contents/"
 
 codesign --timestamp --options=runtime -s "$APP_CERTIFICATE" -v --entitlements ./build/darwin/entitlements.plist "./build/bin/$APP_NAME.app"
 
 productbuild --sign "$PKG_CERTIFICATE" --component "./build/bin/$APP_NAME.app" /Applications "./$APP_NAME.pkg"
+
+echo "Build completed successfully!"

These improvements:

  • Add error handling with set -e
  • Validate required variables
  • Add quotes to the cp command for consistency
  • Add a success message
website/src/pages/changelog.mdx (2)

Line range hint 18-24: Consider adding version comparison links

To make it easier for users to compare versions, consider adding version comparison links at the bottom of each version entry, e.g.:

+ [v2.0.0]: https://github.com/wailsapp/wails/compare/v2.0.0-rc.1...v2.0.0
🧰 Tools
🪛 LanguageTool

[duplication] ~20-~20: Possible typo: you repeated a word
Context: ...pport app names containing spaces. ### Added - Added option to set window class name on Wind...

(ENGLISH_WORD_REPEAT_RULE)


Line range hint 1-1500: Consider adding migration guides for breaking changes

When documenting breaking changes, consider adding links to migration guides to help users upgrade smoothly. For example, in the v2.0.0-beta.44 entry where CSS drag detection was introduced.

🧰 Tools
🪛 LanguageTool

[duplication] ~20-~20: Possible typo: you repeated a word
Context: ...pport app names containing spaces. ### Added - Added option to set window class name on Wind...

(ENGLISH_WORD_REPEAT_RULE)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 8deb8a0 and a1e2041.

📒 Files selected for processing (2)
  • website/docs/guides/mac-appstore.mdx (1 hunks)
  • website/src/pages/changelog.mdx (1 hunks)
🔇 Additional comments (2)
website/docs/guides/mac-appstore.mdx (1)

84-84: LGTM! Proper handling of paths with spaces

The addition of quotes around file paths in the codesign and productbuild commands correctly addresses the issue of handling app names containing spaces.

Also applies to: 86-86

website/src/pages/changelog.mdx (1)

Line range hint 1-24: LGTM! The changelog follows best practices.

The changelog follows the Keep a Changelog format and provides clear categorization of changes. The format is consistent and well-structured.

🧰 Tools
🪛 LanguageTool

[duplication] ~20-~20: Possible typo: you repeated a word
Context: ...pport app names containing spaces. ### Added - Added option to set window class name on Wind...

(ENGLISH_WORD_REPEAT_RULE)

@leaanthony

Copy link
Copy Markdown
Member

Thanks for doing this. Can you please add a link to your GH Profile so the changeling properly credits you. Thanks! 🙏

@cristianrgreco

Copy link
Copy Markdown
Contributor Author

No problem, done

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (1)
website/src/pages/changelog.mdx (1)

Line range hint 1-1979: LGTM! The changelog is well-maintained and follows good practices.

The changelog follows a clear and consistent format, with proper categorization of changes and attribution to contributors. The entries are ordered chronologically with the most recent changes at the top.

Consider adding more metadata to version entries

While the current format is good, consider enhancing it with:

  • Release dates in ISO 8601 format (YYYY-MM-DD)
  • Links to related PRs/issues consistently for all entries
  • Type of release (e.g. Feature, Bug fix, etc.)

Example format:

## [v2.0.0] - 2024-09-22 (Feature Release)

### Added
- Feature X (#123) @contributor
🧰 Tools
🪛 LanguageTool

[duplication] ~20-~20: Possible typo: you repeated a word
Context: ...ntaining spaces by @cristianrgreco ### Added - Added option to set window class name on Wind...

(ENGLISH_WORD_REPEAT_RULE)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between a1e2041 and 5868f26.

📒 Files selected for processing (1)
  • website/src/pages/changelog.mdx (1 hunks)

@leaanthony leaanthony merged commit bd57598 into wailsapp:master Nov 29, 2024
@cristianrgreco cristianrgreco deleted the patch-1 branch November 29, 2024 22:10
@leaanthony

Copy link
Copy Markdown
Member

Thanks for taking the time to do this 🙏

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