I'm having trouble signing a basic Tizen package, here are the steps I've followed:
Installation:
Execute the Tizen studio 3.0 web-ide installer
Accept the license agreement
Use the default SDK and Data location (click install)
Launch the package manager
Install the 4.0 wearable package
Exit the package manager and launch Tizen studio
Create the Project:
Launch with the default workspace
File->new->Tizen project
Select template
Select wearable 4.0
Select native application
Select basicUI
Finish
Create the Certificate:
Tools->certificate manager
Click the "+" button to create a new certificate profile
Name the certificate "TestCert"
Select "Create a new author certificate" and click next
Filename:author
Author Name:Sam
Password:password
Select "use the default Tizen distributor certificate" and click Finish
Exit out of the certificate manager
Try to Build the Package:
Select the project you created earlier
Project->build signed package
I get this console output:
Initialize... OK
Copying files... OK
Signing... java.io.IOException: Invaild password
I am aware of these other stack overflow questions but they do not help me:
tizen studio (x64) - Build Signed Package - Creating package failed - java.io.IOexception: Invalid password
Sign application package with cerificate profile in tizen studio
Can anyone spot what I'm doing wrong?
This was all done on Debian 9.
I am not 100% sure of what I am saying here. It appears that Tizen Studio on Linux uses secret-tool (https://manpages.ubuntu.com/manpages/xenial/man1/secret-tool.1.html) to store certificate passwords. If the Platform Keyring (Gnome Keyring) is not configured properly, secret-tool fails and Tizen Studio does not appear to propagate this failure properly to the user. There are too many variables here, but one should first try running the secret-tool that gets shipped with the Tizen Studio IDE (tizen-studio/tools/certificate-encryptor/secret-tool) and see if it throws any errors when trying to save a password.
Related
I'm trying to publish my .NET MAUI app using a Mac and I'm getting the following error:
A runtime identifier must be specified in order to publish this
project
First, I'm not an experienced Mac user. Second, I'm on a remote rental Mac and I don't have Admin or Sudo privileges.
With that said, I tried to use the command from Microsoft docs but wasn't making any progress due to a few issues with the IP address of the Mac I'm renting, etc.
I then found a similar issue which suggested that I use:
dotnet publish -f:net6.0-ios -c:Release
Using this produced the error above. Someone suggested I add the runtime identifier to the command so I tried:
dotnet publish -f:net6.0-ios -c:Release -r ios-arm64
This gives me an error that indicates that ios-arm64 is not a valid identifier.
I then tried adding the following to the project file which is still not working and throwing the same error:
<PropertyGroup Condition="'$(IsPublishing)' == 'true' And '$(TargetFramework)' == 'net6.0-ios'">
<RuntimeIdentifier>ios-arm64</RuntimeIdentifier>
</PropertyGroup>
Any suggestions how I can publish this app? I'm just trying to create the bundle. I'll then upload it manually.
If your provisioning profile is correct, and you are using VS 2022, try to export the certificate (p12 file) in Keychain of your Mac and import the certificate and profile into VS.
Go to Keychain, click Login, click Certificates on the top bar, then select the certificate, right click it and export as a p12 file, pay attention to remembering the password.
Move the file to your Windows machine, go to Tools -> Options->Xamarin ->Apple Account in VS, and click View Details, click Import Certificate, import the p12 file and input the password.
Unfortunately, you need sudo in order to publish your MAUI app. I had this issue before and I solved it using sudo command.
I think this issue can be fixed in future VS2022 release or when MAUI officially release in coming November 2022.
I am building a small app for Hololens 2. When I choose "Build And Run" in Unity, it makes it close to the end, but I get this error:
BuildFailedException: Failed to export self-signing certificate for appx Package.
Output:System.Security.Cryptography.CryptographicException: Input data cannot be coded as a valid certificate. ---> System.Security.Cryptography.CryptographicException: Input data cannot be coded as a valid certificate.
Here are my build settings:
Other settings:
Unity 2019.4.14f1
Visual Studio Community 2019 16.8.2
What I have tried:
generating a certificate with a password
generating a certificate without a password
executable only build type
D3D Project build type
restarting Unity
installing the certificate on my machine
restarting my computer
Using "Build" instead of "Build And Run". This results in "Build succeeded".
Switching to ARM architecture instead of ARM64
Following deployment instructions at https://microsoft.github.io/MixedRealityToolkit-Unity/Documentation/BuildAndDeploy.html
What do I need to change to get this to deploy successfully?
To fix:
Uninstall all Visual Studio stuff. Visual Studio, Build tools, everything.
Reinstall Visual studio following these instructions: https://learn.microsoft.com/en-us/windows/mixed-reality/develop/install-the-tools?tabs=unity
Install a few additional packages. Visual Studio Installer -> Modify -> Individual Components tab, find "C++ Universal Windows Platform support for v142 build tools (ARM 64)" and "C++ (v142) Universal Windows Platform tools", and select "Modify" in the bottom right.
After that I was able to deploy the package to the Hololens, using the D3D build type and a new build folder.
I have just installed Tizen Studio 2.0 and I was trying to update my old application (version wearable 2.2) with new features.
The target device is a Samsung "Gear 2" (not "Gear S2").
By means of the package manager I installed both the Samsung certificate and the Samsung wearable extension.
I removed all the old certificates and acquired a new one via the certificate manager (Samsung option). The new certificate results active.
From the device manager/file explorer I selected "permit to install applications". The result was en error and an invitation to create and activate a Samsung certificate. Exactly what I had done previoulsy!!!!!!
Trying to install the app via debugger the result was:
[Initializing the launch environment...]
RDS: On
Target information: SM-R380
Application information: Id(Z8KnFDT3ds.ride), Package Name(Z8KnFDT3ds),
Project Name(ride)
[Transferring the package...]
Transferred the package: wgt stream -> /opt/usr/apps/tmp/ride.wgt
[Installing the package...]
path is /opt/usr/apps/tmp/ride.wgt
processing result : FATAL_ERROR [61] failed
spend time for pkgcmd is [94]ms
cmd_ret:61
An exception occurred
(Installing the package... > Fail)
An exception occurred
Unexpected stop progress...
(9.763 sec)"
I have already tried (uselessly) to:
regenerate the .medata file,
to create a new the workspace,
to reinstall Tizen 2.0.,
to create a new certificate,
to install the wgt via sdb.
The time and the date on the Gear 2 are correctly synchronized with my host computer (OS Windows 10).
I noticed an anomaly in my Gear 2 DUID (PB+hcyFaLdbqjuVe+Gcn4vBlSYw=)
Considering what reported at the link: http://developer.samsung.com/gear/develop/getting-certificates/permit the DUID should be in any case preceded by a #1.0 or #2.0. This is not true in my case.
By changing manually the DUID to: 1.0#PB+hcyFaLdbqjuVe+Gcn4vBlSYw= a certficate is apparently correctly uploaded on the target even if the FATAL error 61 persits.
Any idea?
Regards
I have been having insurmountable problems with SDK 2.0 as well. Eventually I decided to roll back to the previous version but was struggling to find out how or where to get it. I got a response from the Tizen support team with the following instructions.
Launch Package Manager
click the "Configuration" icon in the top right corner of the Package Manager window.
Turn OFF the "Auto Update" feature
You will be able to see the list of previous versions of Tizen Studio. Select your desired version and click "OK"
This will prompt you that its going to update the previous version. please follow the UI prompt to uninstall this version and install the previous version.
This may or may not work for you.
I want to build a Tizen in Inity, but I got an error message.
'profiles path in tizen CLI configuration does not exist.'
And the build fails. The '.tizen-cli-config' file was created on my desktop.
I've set the re path, but received the same error message.
Can you confirm that you have created certificate and link that certificate in your unity project.
For How to create certificate refer this
And also confirm you have enabled developer mode in device
Check this
And also confirm that your unity project path does not have any special character. It will be fail if any folder(Directory) name have special character.
Read the Tizen set up documentation from unity docs.
Link : -Unity Documentation for Tizen Set Up
I am using JDeveloper 11g Release 2. I am trying to run a helloworld code on the Android simulator. But i end up having the following error in the console. This is due to some settings that i have failed to set. Can someone help me to add the settings so i could run the app on the Android Console.
The following Android preference configuration is missing or invalid. Set these options in JDeveloper Preferences on the ADF Mobile panel:
Key and Keystore Password
Android SDK Location
Android Platform Location
(oracle.adfmf.framework.dt.deploy.android.deployers.ValidatePreferencesDeployer)
If you haven't keystore for signing android apps right now as for testing purpose. You should select build mode to Debug rather than Release mode.
Application > Application Properties > Deployment > select your android build profiles or create a new one > Click at Edit button > Android Option > Change Build Mode to Debug
You need to install the Android SDK for Android development and Xcode for iOS development.
FAQ for ADF Mobile: http://www.oracle.com/technetwork/developer-tools/adf/learnmore/adfmobilefaq-1866697.pdf
Here you can find the setup guide for Android :
http://docs.oracle.com/cd/E18941_01/tutorials/MobileTutorial/jdtut_11r2_54_2.html
And the one for iOS :
http://docs.oracle.com/cd/E18941_01/tutorials/MobileTutorial/jdtut_11r2_54_1.html
For Android, make sure your emulator emulates version 4.0 or higher in order to avoid :
The Android emulator emulates ARMv5, which is not supported. The emulator must support ARMv6 or newer
If there is also an error above this stating that it can't write the cwallet.sso try closing Jdeveloper and running as administrator.