I run this pnpm tauri build --features online --target aarch64-apple-darwin and it seems to bundle the DMG successfully but when I open the dmg it says the file is corrupted and when I click on the quesiton mark it says the following The app has been modified, and its code does not match the original signed code. The app may be broken or corrupted, or it may have been tampered with. If you think that an app has been damaged or tampered with, you should delete it by dragging it to the Trash. I have looked online and it seems as though I may have to get a apple developer license. I wanted to ask is this the case? and if so once I get my apple developer license what file do I have to specify in tauri.conf?
#Issues with DMG Bundling/Generation
lapis pecan
last heath
You shouldn’t need a license to produce DMGs.
silk comet
what kind of errors do you get when you try to open the .app bundle?
Also, if you actually want to share the app with users that aren't friends & family you really do need a license. Especially arm apps on arm devices where opening unsigned apps is way harder than intel apps.
We have a guide for that btw: https://tauri.app/v1/guides/distribution/sign-macos/
lapis pecan
This is just for family and friends
silk comet
i am not sure how it translates to the .dmg, but on a .app bundle they could run xattr -c my-app.app and then they should be able to start it. But they have to run this cli command on their system, you can't run it on your own before distribution.
lapis pecan
I guess im just confused on the steps after running pnpm tauri build --features online --target aarch64-apple-darwin because this the message that I get Finished release [optimized] target(s) in 2m 11s Bundling my-app.app (/Users/j-supha/Desktop/ADV/my-app/src-tauri/target/aarch64-apple-darwin/release/bundle/macos/my-app.app) Bundling my-app_0.1.0_aarch64.dmg (/Users/j-supha/Desktop/ADV/my-app/src-tauri/target/aarch64-apple-darwin/release/bundle/dmg/my-app_0.1.0_aarch64.dmg) Running bundle_dmg.sh Finished 2 bundles at: /Users/j-supha/Desktop/ADV/my-app/src-tauri/target/aarch64-apple-darwin/release/bundle/macos/my-app.app /Users/j-supha/Desktop/ADV/my-app/src-tauri/target/aarch64-apple-darwin/release/bundle/dmg/my-app_0.1.0_aarch64.dmg right now I am just opening the dmg file after this has been done. IS there another step that I need to do/ Is there something that I am misunderstanding?
Ideally wha tI want to be able to do is send a file to someone else who is on an M mac so that they can open and see my application
silk comet
well, if you don't want to spend 100$ a year (which i'd understand tbh) that's all you can do on your side.
you could try building a intel/x86_64 binary instead. macOS is a bit less strict about those but it requires rosetta to be installed on the user system (it will automatically prompt for installation if it's missing)
lapis pecan
Lets say I (begrudgingly) paid the $100 a year to Apple. What would I have to include here ```DMG license file: A license that is added to the .dmg file. Configure by the tauri.bundle.macOS.license property.
that's unrelated to the problem
you can add usage licenses to your dmg bundle
similar to MIT in github repos
and that doesn't need a certificate
lapis pecan
that's unrelated to the problem
Is there a way then to pass the DMG and or .app file along to specified M mac users at the moment (sorry for all the questions 🙂 ). For now is the best way just passing the .app file along with this command xattr -c my-app.app
silk comet
ues, just pass them the .app (or tar.gz or zip or whatever) and let them run this command in their terminal (again, must happen on their machine)
Then the app should be able to be opened
Or i guess, they still need the "normal" workarounds like enabling apps from all sources, and maybe right click -> open instead of double click. I don't use macos myself enough to be 100% sure about that part.
lapis pecan
Understood will try all this out. Thank you so much for your help. You guys have built something truly awesome 