i want to push one tango project apk into google playstore, what is steps to do it, Is it same like pushing android apk? How can it differentiate as tango?
Thanks in advance.
Deploying applications using the Tango framework to Google Play requires only one additional step to the normal Android distribution process. To make sure your application can only be installed by Tango compatible devices, add the following line to your application's manifest file.
<uses-library android:name="com.projecttango.libtango_device2" android:required="true" />
Related
I use the Crashlytics framework for crash collecting in iOS Apps.
When you use the framework, a "Build Phase" is added to your target that runs /Fabric/Fabric.framework/run <big-hex-blob> <another-even-biger-hex-blob>.
I'd love to know that these actually do – I'm not entirely happy with having external vendors' tools monkey about with my build, I'm old school like that.
Mike from Crashlytics and Fabric here.
The run script build phase is used, along with your <APIkey> and <BuildSecret>, to automatically handle the uploading of dSYMs so that you, and other developers, never need to manually upload one.
Similarly, the /Crashlytics.framework/submit command is used for distributions through Beta, our beta distribution service.
I need to distribute my apps to testers prior to submitting them to the store(s). Nativescript builds an apk file that is easily distributed to Android testers. Is TestFlight the recommended way to distribute iOS apps? And should I use the xcode project file to build the app in Xcode in order to submit it to TestFlight. That method seems counter intuitive.
Yes, ideally you would use TestFlight. It's also a perfect way for you to test your distribution build/signing etc since you would upload the exact same build that will end up on the App Store. In fact, if your testing goes well with your users, you can submit the same build that you've already uploaded for TestFlight to the reviewers for the App Store, you don't even need to upload a new build.
As #Dave Wood mentioned, yes, TestFlight should be the way to go forward as you do not need to re-build the app to submit for review to Apple.
Answer to your next question should I use the xcode project file to build the app in Xcode -
No
You can use the below commands to build and publish app to Apple store.
From the root folder of your app
tns build ios --release --for-device --bundle <Your Provision Profile>
this will show the path where it has created the .ipa file, then
tns publish ios --ipa <.ipa file>
this will ask your Apple ID and App Specific password and will process the actual App based on your appid mentioned in your package.json.
You can change the app version and App name in info.plist inside App Resources->ios folder.
Thanks. I realized this was the answer after I posted the question. I'm new to NativeScript, but not to iOS development. It occurred to me that once the app is uploaded to App Store Connect, I still control the activities of either posting or setting up TestFlight. Thank you.
guys.
First goes the questions.
I need to combine different Xcode projects for iOS and watchOS. And I need automation for this.
Is it possible to set reference in iOS-Xcode project to watchOS-Xcode project, and setup outer project to build target iOS app with embedded watchOS app, by using targets of inner project? Is it possible to do such a thing with workspaces?
Are there exist some command line tools for managing Xcode project, like adding targets, changing build settings, setup build phases, add resources and so on?
Problem summary.
I'm currently developing video game with Unity3D for iOS and want to make a companion application for watchOS. The problem is that Unity doesn't have any built-in support for watchOS, thus I have to care about integration of watchOS part by myself.
I have Unity project for the game itself and different Xcode project for watchOS part of the game. Now I combine Unity-generated Xcode project with the necessary parts of watchOS project manually: I create WatchKit App target, then import necessary resources from the separate watchOS-project, setup build settings as required - and that do the thing, I get the game with Apple Watch support.
The thing is, that I need to do automation for this process. But I haven't found some useful information on this topic neither here (on stackoverflow), not did on official apple developers' site, not on unityanswers.com, nor in Xcode documentation.
Thanks in advance.
I am developing a hybrid mobile application in dot net, i have created my own custom plugin using x_code and phone_gap . what are the ways to integrate my plugin to dot_net project.
This is an older question, but maybe this answer can help someone down the road.
This is the approach I have taken with DevExtreme to use a custom plugin and at the same time use the PhoneGap build process.
Upload your plugin to your GitHub Account.
Update your Config.xml
<gap:plugin name="your git hub package url" source="git"/>
(instead of name="" use spec="" and source="git")
NOTE: as of this post there is a bug in DevExtreme that if you attempt to look at Project Properties > PhoneGap Tab Studio will crash. DX is aware and they are suppose to fix it.
Build a custom template (this is the PhoneGap build portion)
Build your project.
I am learning phonegap thru online tutorials.
I was creating facebook integration dummy app in xcode using phonegap by following step by step tutorial given at https://github.com/davejohnson/phonegap-plugin-facebook-connect
I was able to setup everything but one step where I was asked to add CordovaLib class path to XCODE was not working for me, I tried searching CordovaLib with downloaded and extracted phonegap(2.0.0) but couldn't find same.
At last, after spending good amount of time on google I could get CordovaLib from GITHUB and able to compile my project and make it work.
My question is, if CordovaLib is must for phonegap integration with Xcode, why is it not shipped with phonegap download ?
What is the best way to get CordovaLib in future for newer phonegap versions ?
There is no need anymore.
Note: Starting with Cordova 2.2, the project will have a copy of CordovaLib within it instead of having a dependency on the copy of CordovaLib from your Cordova installation.
guide_getting-started_ios