Skip to content

Conversation

@Sky-walkerX
Copy link
Contributor

closes #12674

@Sky-walkerX Sky-walkerX requested a review from a team as a code owner June 15, 2025 19:20
@github-project-automation github-project-automation bot moved this to 📬Proposal in Roadmap Jun 15, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Jun 16, 2025

Package Changes Through 825fb73

There are 8 changes which include tauri-bundler with minor, tauri-cli with minor, tauri-codegen with minor, tauri-utils with minor, @tauri-apps/cli with minor, tauri with minor, @tauri-apps/api with minor, tauri-runtime-wry with patch

Planned Package Versions

The following package releases are the planned based on the context of changes in this pull request.

package current next
@tauri-apps/api 2.5.0 2.6.0
tauri-utils 2.4.0 2.5.0
tauri-bundler 2.4.0 2.5.0
tauri-runtime 2.6.0 2.6.1
tauri-runtime-wry 2.6.0 2.6.1
tauri-codegen 2.2.0 2.3.0
tauri-macros 2.2.0 2.2.1
tauri-plugin 2.2.0 2.2.1
tauri-build 2.2.0 2.2.1
tauri 2.5.1 2.6.0
@tauri-apps/cli 2.5.0 2.6.0
tauri-cli 2.5.0 2.6.0

Add another change file through the GitHub UI by following this link.


Read about change files or the docs at github.com/jbolda/covector

Copy link
Contributor

@Legend-Master Legend-Master left a comment

Choose a reason for hiding this comment

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

Thanks!

Since I'm not familiar with how this really works on macOS, I'll ask @FabianLars to review as well

@Legend-Master Legend-Master requested a review from FabianLars June 16, 2025 15:13
@Legend-Master Legend-Master merged commit 8ee14a8 into tauri-apps:dev Jun 16, 2025
14 checks passed
@github-project-automation github-project-automation bot moved this from 📬Proposal to 🔎 In audit in Roadmap Jun 16, 2025
@Legend-Master
Copy link
Contributor

I wonder if we should also update the default app id in create-tauri-app as it defaults to com.tauri-app.app which could cause problems if the user just wants to experiment with things without changing that first

@Sky-walkerX
Copy link
Contributor Author

I wonder if we should also update the default app id in create-tauri-app as it defaults to com.tauri-app.app which could cause problems if the user just wants to experiment with things without changing that first

Maybe we could prompt the user to set a custom appId, or just generate one from the project name

@Legend-Master
Copy link
Contributor

Technically, we are doing that, just thinking we might want to get rid of the .app part by default

image

@lucasfernog
Copy link
Member

this is actually a breaking change, there's a bunch of apps ending with .app that do not really care about the config paths (i'm actually working on one of those :D )

);
std::process::exit(1);
} else {
log::warn!(
Copy link
Member

Choose a reason for hiding this comment

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

I would always warn instead of exiting like above

@Hacksore
Copy link
Contributor

Hacksore commented Jun 17, 2025

Yeah I suppose if you are not caring about macOS and you have a .app your builds will now fail which is not desired.

An opt-in CLI flag would not make sense to me but has tauri considered something like compatibility dates in configs so we can introduce semi-breaking changes like this?

How cloudflare does it via Compatibility dates.

@FabianLars
Copy link
Member

What about those that wkwebview creates?

True about the braking change, didn't really think about that but imo we should still really consider making this a hard error in a future major. (With an opt-out for migrators ig)

@Legend-Master
Copy link
Contributor

Legend-Master commented Jun 17, 2025

So I guess we just warn about it for now? I'm not sure if the directory is not usable or just can't be used in finder, if it's just in finder, I guess just a warning would be a better choice for now

@Sky-walkerX
Copy link
Contributor Author

So should I do log::warn and remove log::error and exit from the code block ?

@Legend-Master
Copy link
Contributor

Yeah, let's do that, we can always make it a hard fail in the future

@Sky-walkerX
Copy link
Contributor Author

Yeah, let's do that, we can always make it a hard fail in the future

PR -> #13627, please check

@lucasfernog
Copy link
Member

So I guess we just warn about it for now? I'm not sure if the directory is not usable or just can't be used in finder, if it's just in finder, I guess just a warning would be a better choice for now

it's still usable, but Finder shows it as an app and you'd need to actually rightclick -> show package contents to open it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: 🔎 In audit

Development

Successfully merging this pull request may close these issues.

[bug] Prevent .app in identifier

5 participants