I installed Titanium Studio properly and when I execute it, gives me an error like this
"Failed to load the JNI shared library C:\Program files\Java\JDK 1.7.0_17\bin\...\jre\bin\server\jvm.dll"
NOTE: I have java 64bit version.
It might be the issue with the SDK. In order to run Titanium Studio and the Titanium Mobile SDK successfully, your system environment must meet the following condition
For Windows, the 32-bit version of Java JDK is required regardless of
whether Titanium is running on a 32-bit or 64-bit system.
Please read System Requirements before installing the Titanium Studio.
I hope this will help you
Related
I am running Mac OS Catalina, and have Visual Studio version 8.3.8 installed. Before installing Catalina I had no problems building and running my code in Visual Studio.
I don't get any errors when building the code, but each time I try to run my code I get the following dialog popup
Could not connect to the debugger
And I get the following in my terminal:
bash: /Library/Frameworks/Mono.framework/Versions/6.4.0/bin/mono32:
Bad CPU type in executable
I suspect that Catalina doesn't run 32 bit programs, is there a way around this? I thought that Mono from version 5.2 defaulted to 64 bit.
I ran into this issue while using the following settings:
Windows 10
Visual Studio 2019
Macbook Pro
macOS Big Sure 11.4
Visual Studio for Mac (latest)
XCode 12.5
When trying to debug my Xamarin app for IOS and connect my mac in visual studio I had to follow the following steps.
Install mono - https://www.mono-project.com/docs/about-mono/supported-platforms/macos/
Open Visual Studio for Mac (on mac)
Open XCode (mac)
Connect To mac through Visual Studio
After that I stopped getting the connection error.
I know this isn't your exact question, but maybe it can help someone in the future.
I experienced the same problem when trying to debug practically any app in VS Mac. I am now using 2022 and the same issue persisted since using 2019. If trying to debug your code locally, what you can do is to run your app first without debugging. Then, attach the debugger to the executed process. So, if your web app is executing in let's say, "Chrome", then search for that process, usually, it will be the name of your app (it's a dotnet process), then simply attach the debugger to it. Then, you should be able to set breakpoints and hit them.
Hope this will help anyone working with VS for Mac.
In the process of creating an Hybrid app while adding other environmenent i mean adding apple and android thus it requires the necessary sdk to be preinstalled in eclipse help pls ?
MobileFirst Studio generates for you the native project for each environment.
iOS: an Xcode project is generated. You then need to open it in Xcode, which requires a Mac.
Windows/Windows Phone: a Visual Studio project is generated. You then need to open it in Visual Studio, which requires a PC running Windows 8 or above
Android: for the native project to be generated, you need to:
either install the Android ADT plug-in for Eclipse
or setup Android Studio and open the project there
Much like your previous question, the answer to this is in the Getting Started training materials. Please read them: https://developer.ibm.com/mobilefirstplatform/documentation/getting-started-7-1/foundation/setting-up-your-development-environment/
I want to do Windows Phone development with Titanium Studio.
I followed https://wiki.appcelerator.org/display/guides2/Getting+Started+with+the+Windows+Phone+SDK#GettingStartedwiththeWindowsPhoneSDK-UsingStudio(Preview) in order to get the Windows plugin. After a required restart of the software, the Windows option apears in the Deployment Targets when creating a new project.
Unfortunately, for all Titanium SDK Versions I have installed, 3.5.1.GA, 3.5.0.GA, 3.4.0.GA, 3.3.0.GA, I am getting an error like "Titanium SDK v3.5.1.GA does not support the Windows platform".
So I basically cannot create projects for Windows Phone.
I am using Titanium Studio 3.4.1 and followed the installation tutorial, though I deleted the SDK path after setting it (it is the default path, setting a value caused an error message, also I left the publisher GUID and Windows Store Certificate empty, since I just want to develop and don't have publishing credentials yet).
How can I create an app that runs on Windows Phone, too?
Edit:
I add some images to show the problem better. In the last step, I don't have the possibility to create a Windows project in Titanium Studio.
2nd edit:
As per Eduard's answer, I skipped https://wiki.appcelerator.org/display/guides2/Getting+Started+with+the+Windows+Phone+SDK#GettingStartedwiththeWindowsPhoneSDK-WindowsPlatform(Preview) and had to do it. Now I got Titanium SDK 4.1.0.v2015... and I get the option.
Unfortunately, it still does not work.
https://jira.appcelerator.org/browse/TISTUD-7171
So I also need to update Titanium Studio.
Well, I guess mobile development has to be buggy and cumbersome, at least that is my experience so far with various (cross-platform) products.
Try opening the solution generated in Visual Studio to attempt packaging the .sln to .appxupload to upload it to the Windows Store. Hopefully that will serve as work around until Titanium has full support for Windows (very likely 4.0.0 or 4.1.0 Titanium SDKs).
I am new to the Titanium or any other cross platform SDK. I am facing issues with the setup of Titanium Studio. I followed steps as below:
Installed NodeJS
Installed JDK 1.7 update 55 32-bit
Installed Titanium Studio 3.2.3
After first launch of Titanium Studio it installed the Titanium SDK, Alloy, Titanium CLI and other updates. In the preferences,
Titanium SDK Path
C:\Users\<UserName>\AppData\Roaming\Titanium\
ANDOIRD SDK Path
E:\adt-bundle-windows-x86_64-20131030\sdk
Environment Variables are set as follows:
ANDROID_SDK
E:\android-sdk-windows
ANDROID_SDK_HOME
c:\users\<UserName>
JAVA_HOME
C:\Progra~2\Java\jdk1.7.0_55
Path
C:\Program Files\TortoiseSVN\bin;c:\Progra~2\Java\jdk1.7.0_55\bin;C:\Program Files\nodejs\;C:\Program Files (x86)\Git\git-cheetah\..\bin;E:\android-sdk_r22.3-windows\android-sdk-home\tools;E:\android-sdk_r22.3-windows\android-sdk-home\platform-tools;C:\Program Files (x86)\Git\bin;C:\Program Files\nodejs
There are two problems here:
Alloy is not available in the new project template and
Android SDK is not available in the project template
On Windows Min JDK Version supported is 6 (aka 1.6) rev 10 and Max JDK Version supported is 6 latest revision.
The 32-bit version of the JDK is required regardless of whether Titanium is running on a 32-bit or 64-bit Windows system.
On Windows, Studio contains its own JRE, meaning you do not need to install the JDK before installing or launching Studio but will need it to use the Titanium SDK.
Titanium Studio prompts you to install the JDK when installing the Android SDK from the Dashboard on Windows.
For more details please check this link.
Background
We're using System Center 2012 to deploy a Windows 8 Metro-style application to Samsung slates in the field running Windows 8 Enterprise x64. The slates are joined to the domain and have a persistent DirectAccess connection back to it, allowing System Center to push applications and updates to the devices.
We have to deploy our application to potentially hundreds of devices in the field, which is why we went the System Center route. The code signing cert is installed on every device using Group Policy. To deploy the application, you simply provide the package output and specify the collection of devices to install it on. The app just shows up on the device in a few minutes.
The problem we're having is that when System Center deploys our application, the SQLite dependency is lost and none of our data access works.
About our project
Our application is a WinJS application that uses SQLite as a backend. However, all our data access code is in a C# WinMD project which the WinJS project references. We're using the sqlite-net library to talk to SQLite - we included the source for that in our C# project.
In Visual Studio, we installed the SQLite for Windows Runtime extension as described in Tim Heuer's article. The Metro application references this.
Testing using other deployment methods
SQLite data access from the application works fine when you debug or run it locally - in both Debug/Release and x86/x64.
The app packaging process provides a PowerShell script that you can use to install the application and a developer license if necessary. When installing our app using the PowerShell script, SQLite data access also works fine. Verified this by packaging and installing both Debug/Release and x86/x64 versions of the app.
Troubleshooting
When the application first tries to use SQLite, we see an exception about it not being able to find the sqlite3.dll.
We've tried/verified the following:
Confirm that we're deploying a Release/x64 build
Examine the appx in WinRAR and verify that it contains the sqlite3.dll
Reference the "SQLite for Windows Runtime" extension from the C# project instead of the WinJS project
Also reference the C++ runtime, this caused System Center to fail when deploying the app. Don't know why yet, but looking into it.
UPDATE
The issue is that System Center is having trouble deploying the Visual C++ Runtime Library dependency that the SQLite library needs. So unfortunately this isn't a programming question anymore. We're getting some help on this and I'll post the fix.
I wanted to post the details of a temporary fix that we're going with. We've also gotten closer to the root of the problem, so I wanted to provide those details as well.
Recap of Issue
When referencing the Visual C++ Runtime Package from our Metro project, System Center is unable to deploy the application to the devices because there is a problem deploying the proper version of the dependency for the appropriate architecture and build flavor.
Our development machines running Visual Studio 2012 (and packaging the project for deployment) are using a newer version of the Visual C++ Runtime (50727) than what is available in a fresh installation of Windows 8 (50712).
Worked with the System Center team and confirmed that this was a bug in the version we were using and has already been addressed in future builds. We're going to work on upgrading the environment but that will take a couple of weeks.
Workaround
I confirmed and tested the following workaround:
Remove the reference to the Microsoft Visual C++ Runtime Package from the Metro project
Install the x64 version of the Visual C++ Redistributable for Visual Studio 2012 - http://www.microsoft.com/en-us/download/details.aspx?id=3
Deploy the application
Works like a charm because the correct version of the dependency is there already. Obviously not a long term solution if we choose to also target x86 and ARM, but will get us over this hump.