Hey guys,
Error build (os x)
Windows works fine.
P.s.
Added achievements
Hey guys,
Error build (os x)
Windows works fine.
P.s.
Added achievements
Is this plugin a beta? I can’t find anything about it on the forums.
Yes
@joxsea, have you tried recently? There were changes to the store overnight and you might have hit an outage while the work was going on. Please try again.
@nick_sherman, We are asking some of the developers who are already on Steam to give the plugin a go to try and find problems and such. Depending on how that testing goes, we plan to announce it on the blog when it’s more ready for public consumption. We will make a big to-do about it when it’s ready for the world to use!
Rob
@joxsea, this appears to be a code signing issue on Mac. As in Valve’s *.dylib library won’t pass Apple’s code signing’s validation process. We’re investigating how to best resolve it. Sorry about the inconvenience.
For the moment, if you just want to test Steam support on Mac, you can build your Mac app by *NOT* code signing it.
So here’s what the issue is. This build error will happen if you try to code sign your Mac app using a “Mac App Store” certificate. This is *not* what you want to do… and here’s why:
What you need to do is sign your app with an Apple “Developer ID Application” certificate. This certificate is intended for apps that will be distributed outside of the Mac App Store, such as Steam… or as a download from your own website. Info about this certificate can be found at Apple’s website here…
https://developer.apple.com/developer-id
Once you’ve acquired a “Developer ID Application” certificate from Apple’s developer portal and installed it on your machine, you can then build and sign your app as follows:
In the Corona Simulator’s “Build for OS X” window, select “None” from the “Provisioning Profile” drop-down box.
Click the “Build” button. (Note that this app will not be signed.)
Open the “Terminal” application.
Run the following command line to sign the app yourself.
codesign --deep -f -s “Developer ID Application: <YourCompanyName>” <PathToYour.app>
Note that you need to fill in the above <YourCompanyName> and <PathtoYour.app> with the appropriate text. And the “Developer ID Application: <YourCompanyName>” will be the full name of your certificate you see listed in Apple’s Keychain application once the certificate is installed. Once signed, your app will no longer be blocked by OS X’s “Gatekeeper” feature.
I hope this helps!
Is this plugin a beta? I can’t find anything about it on the forums.
Yes
@joxsea, have you tried recently? There were changes to the store overnight and you might have hit an outage while the work was going on. Please try again.
@nick_sherman, We are asking some of the developers who are already on Steam to give the plugin a go to try and find problems and such. Depending on how that testing goes, we plan to announce it on the blog when it’s more ready for public consumption. We will make a big to-do about it when it’s ready for the world to use!
Rob
@joxsea, this appears to be a code signing issue on Mac. As in Valve’s *.dylib library won’t pass Apple’s code signing’s validation process. We’re investigating how to best resolve it. Sorry about the inconvenience.
For the moment, if you just want to test Steam support on Mac, you can build your Mac app by *NOT* code signing it.
So here’s what the issue is. This build error will happen if you try to code sign your Mac app using a “Mac App Store” certificate. This is *not* what you want to do… and here’s why:
What you need to do is sign your app with an Apple “Developer ID Application” certificate. This certificate is intended for apps that will be distributed outside of the Mac App Store, such as Steam… or as a download from your own website. Info about this certificate can be found at Apple’s website here…
https://developer.apple.com/developer-id
Once you’ve acquired a “Developer ID Application” certificate from Apple’s developer portal and installed it on your machine, you can then build and sign your app as follows:
In the Corona Simulator’s “Build for OS X” window, select “None” from the “Provisioning Profile” drop-down box.
Click the “Build” button. (Note that this app will not be signed.)
Open the “Terminal” application.
Run the following command line to sign the app yourself.
codesign --deep -f -s “Developer ID Application: <YourCompanyName>” <PathToYour.app>
Note that you need to fill in the above <YourCompanyName> and <PathtoYour.app> with the appropriate text. And the “Developer ID Application: <YourCompanyName>” will be the full name of your certificate you see listed in Apple’s Keychain application once the certificate is installed. Once signed, your app will no longer be blocked by OS X’s “Gatekeeper” feature.
I hope this helps!