I would like to start working on an XCode iOS project on my iMac and then, in few days, move it into my MacBook Air and continue working from there whilst keeping and accessing to the source code version of the initial repository (the one started on the iMac).
Is this possible? And if so is there any tutorial/guide I can follow?
Use a remote git server, like Github or Bitbucket.
Here you find all the info you need
https://help.github.com
Related
In Production, IBM MobileFirst server running with version 7.1.0.00.20180425-1124 and Project war file with version 7.1.0.00.20180425-1124.
Recent deployment of project war was deployed with 7.1.0.00.20161006-0540, unfortunately.
iOS throws below error:
{"error_description":"Client authentication failed","error":"invalid_client"}
Rolled back the deployment to avoid issues.
While investigating, there was an APAR with similar fix but the version used in the deployment doesn't include this APAR.
Question 1: If same version(7.1.0.00.20180425-1124) of MF Plugin used to build Project .war, will this issue be addressed.
Question 2: Where can I download the Eclipse Plugin of 7.1.0.00.20180425-1124?
Thanks in advance
It is not clear what steps you took to update your server. In your MobileFirst server Operations console , if you see the version as "7.1.0.00.20161006-0540" , then you should definitely update.
If that is the case, merely building a new project runtime war file in latest MobileFirst Eclipse Studio and deploying it will not help. The iFix level in the server will have to be updated too. You can use Server Config Tool or ANT scripts to update your iFix level as well to the latest while you deploy the new runtime war.
You can download the latest versions of the iFix ( Server and Studio plugin) in FixCentral.
Finally achieved by clearing out the keychain items and defaults which work light library has been internally maintaining.
So what's happening behind the scenes is the work light client is creating and maintaining some keychain items and also few user defaults. This is done for storing some information like session id's and stuff. Sometimes the data in the keychain or defaults is getting corrupted during the initial work light handshake with MFP server. In this scenario we get the above error. Once we clear them out and kill the app and launch again. the app will now behave as a new device.
I'm brand new to xamarin world (as well as visual studio). I've forked xamarin-evolve app 1 and trying to build and deploy in my local android device.
In documentation, under "Mobile App" section, its mentioned:
Simply restore your NuGet packages and build the application.
As a beginner, I'm looking for a bit more explanation how to build and deploy this project locally in my android device. So that I can play with it.
I would truly appreciate any cooperation.
Thanks.
When you Open up src/XamarinEvolve.sln, do the dollowing steps :
Clean the project solution.
Delete the bin & obj folder in XamarinEvolve.Android, XamarinEvolve.iOS and XamarinEvolve.UWP.
Right click on your Project Solution, then click the Restore NuGet packages.
Deploy the XamarinEvolve.Android project in your device.
Effect.
First of all, I am developing a Cordova app for Android and iOS, primarily.
I was using the deprecated version of the Phone gap push plugin:
https://github.com/phonegap-build/PushPlugin
Now I am using the new version:
https://github.com/phonegap/phonegap-plugin-push
And all my code is also using the new push plugin; I seem to not be able to get rid of the old push plugin completely and it sucks :(
It is beyond me how the old push plugin has a version number of 2.5 whereas the new push plugin has a version number of 1.5 or 1.6.. But moving on.
I am running the app on Android, and everything is ok. The app is running and working as supposed to. I am also successfully receiving notifications.
On iOS, also, everything was working as supposed to till give or take a month ago; but today when trying to deploy on an iOS device using Taco remote build from a windows pc (visual studio) to an apple macbook pro, I began facing many problems.
I then noticed that in the config.xml of the application (the one in the root of the project) there were both the old and the new push plugin. I mistakenly deleted the new one (because of the misleading version numbers; I thought it was in fact the old one). It seemed to run properly for a bit (on both Android and iOS) but after a while, I noticed that in reality the app was not going to work properly as it needed the new push plugin and it was not being found. So I deleted the old push plugin and installed the new push plugin (which happened to be also a more updated version of the new push plugin that I previously had).
Presently, my problem is that when running via taco remote build, the app manages to successfully deploy on an iOS device (iPhone 6) - so yes the remote build seems to be happening correctly!, however the app seems to not be recognising/locating/finding the new push plugin when running. I am suspecting that the new push plugin is not being transferred from visual studio on my windows pc into my apple macbook pro through the taco remote build.
In this directory: /Users/Jurgen/.taco_home/
I can see the build, with all the generated files. In the outermost plugins folder I can see the phonegap-plugin-push folder referring to the new push plugin:
/Users/Jurgen/.taco_home/remote-builds/taco-remote/builds/16880/cordovaApp/plugins/phonegap-plugin-push
Going further into the directory, into the platforms folder/ios/www/plugins etc, there is no phonegap-plugin-push:
/Users/Jurgen/.taco_home/remote-builds/taco-remote/builds/16880/cordovaApp/platforms/ios/www/plugins/-----
I think this might be the cause of the problem: though I am not 100% sure.
I thought that the iOS build most probably uses the plugins folder from the www folder inside the iOS folder and not the outermost (in the first directory shown above): And since the push plugin was nowhere to be seen inside there; that could have been the problem, even more so when bearing in mind that the .xcodeproject file resides in the same 'ios' folder.
So what I did was manually copy the push plugin folder into the innermost directory; which didn't work either. Even if it did, it does not really make sense and is highly inconvenient.
What can I do to ensure that the plugin is transferred into the iOS build with taco remote build? Could the problem be something else rather than what I suspect?
I am completely stuck; so any help would be greatly appreciated!
It sounds like the remote project is confused. Try this to see if it helps:
On your non-mac machine, ensure that only the correct plugin is referenced. This includes both config.xml and in the plugins folder. Consider removing the plugin entirely, then re-adding the correct version. If other plugins specify a dependency on the push plugin in their plugin.xml then that may also cause problems, especially if the biggest version number is not the latest version. You may need to remove those plugins too.
Once that is done, perform a clean build. Via taco-cli this would be taco build ios --clean, with whatever other device etc flags you want. Using Visual Studio you would go to build -> clean i believe.
This should copy your project in its entirety again, and avoid issues with conflicting plugin versions partially persisting.
I'll be working in a team doing phonegap applications for the first time.
For a super simple boilerplate app shared by a team of 3, should I be including the entire project (i.e. all the directories):
app
--merges
--platforms
--plugins
--www
Having had user specific issues with conflicts which arise with iOS builds (and I'm assuming android builds), should I be adding the platforms directory in the .gitignore? Am I correct in assuming that all builds should be done by the user and not rely on someone else's phonegap build-ed versions of the app?
In my project we only commit the www folder and a windows batch file (We develop on Windows) that is the responsable for install automatically each plugin that the app needs.
When a new plugin is added, we add a new entry to that file.
When a new developer wants to make his developt enviroment with the app, him creates a new proyect and imports the www folder. After that, he runs the local build command and later runs the custom porject plugin file.
I am using Xcode 4.2.1 and I have this problem running an existing application on the iOS simulator:
svn: The path '.' appears to be part of a Subversion 1.7 or greater
working copy. Please upgrade your Subversion client to use this
working copy.
/Users/me/Library/Developer/Xcode/DerivedData/myproject-dxfzldckuqdmlrghowwkdrbgoigy/Build /Intermediates/myproject.build/Debug-iphonesimulator/MyProject.build/Script-9567AEA113C59633000AA291.sh: No Subversion revision found at /Users/me/Library/Developer/Xcode/DerivedData/myproject-dxfzldckuqdmlrghowwkdrbgoigy/Build/Intermediates/myproject.build/Debug-iphonesimulator/MyProject.build/Script-9567AEA113C59633000AA291.sh line 32.
Building revision
Command /bin/sh failed with exit code 1
I have a Subversion server 1.7.1 installed and also on the client side I upgraded to 1.7.1.
I did a svn upgrade and then I get this error in Xcode.
If I repeat the svn upgrade on the terminal I get the message Can't upgrade '...' as it is not a pre-1.7 working copy directory.
So what is wrong? How an I solve the problem?
Xcode doesn't yet support SVN 1.7. Only 1.6 is supported. In order to fix your problem, you'll need to switch to using an SVN 1.6 compatible working copy.
Since SVN 1.7 client is unable to work with 1.6 working copies at all, you'll need to remove SVN 1.7.x from your client and revert to 1.6. (Or perhaps just adjust your PATH so the SVN 1.6 tools are first.) Once 1.6 is back, delete or move aside your existing working copy and check out a fresh copy with SVN 1.6. Now Xcode should be able to work with your working copy.
Note that you can freely use SVN 1.6 client with an SVN 1.7 server. Some of the newer features won't be available, but it will work. There's no need to downgrade the server or your server-side repositories.
Keep an eye on the Xcode release notes in updates as I'm sure Apple will note when Xcode is capable of using SVN 1.7. When a 1.7 compatible release of Xcode becomes available, it should then be safe to upgrade your client to 1.7 and migrate your working copy again.
There is a post that appears to imply that you can fool XCode into using svn 1.7 client by changing your PATH and setting up a couple of soft links in strategic places. Unfortunately, the post is in Chinese. Fortunately, Google translate and the presence of UNIX commands make it possible to decrypt what the post is saying. I will try it in the next few days, and update the answer if anything useful comes out of this exercise.
EDIT: I tried the steps from the post, and it worked. Here is what I did:
Downloaded and installed svn client 1.7.2 into /opt/subversion
Added /opt/subversion/bin to my PATH in .bash_profile
Created a backup directory /Developer/usr/bin/orig.svn
Moved /Developer/usr/bin/svn* to /Developer/usr/bin/orig.svn
Ran ln -s /opt/subversion/bin/svn* /Developer/usr/bin/
After that I re-started XCode, went to Organizer, and was able to attach a working copy of a checkout created with svn 1.7.2 client. Organizer showed a green dot next to the repository, displayed a list of revisions, etc., so at this point I believe that the trick has worked.
You can download and install a binary package from http://www.wandisco.com/subversion/download#osx
The package will install to /opt/subversion while the xcode version of SVN is installed in /usr/bin. If you prepend /opt/subversion/bin to your path variable, it will be chosen instead of the xcode version.
If you don't want to mess with your path, you can just alias one version or the other. man alias for details.