xamarin ios project properties - ios

I am having a strange issue with a xamarin IOS project. On one machine when you go to the ios project -> properties. It shows the options like this:
IOS Project Properties Wrong
In the other machine's project the properties look like this:
IOS Project Properties Correct:
You will notice that the IOS Application tab is visible in this project and the iOS Build section has a General and Advanced tab. Why doesn't the other project have this. On both machines I just created a Cross platform PCL template project. Both machines have the latest xamarin installs. What am I doing wrong here?

I figured this one out. The issue here is that with visual studio 4.5 they changed the way that the projects worked. For me personally I cannot deploy xamarin ios. Because of the ITMS-90096 error. Even when I set the images in the info.plist file I still get errors. I will instead revert back to release 4.4 until I can properly deploy to the app store.
Xamarin Release Notes

Related

Can't get App Icons to work for iOS with Xamarin

I have tried everything I have been able to find to get these app icons to work for iOS. No matter what I do, they will not appear, I am stuck with the default Xamarin icons. I even tried making an entirely new project to start fresh with it, and I am still stuck with the default Xamarin icons. I have to be missing something. I have all of the icons in the AppIcon Assets Catalog. The Info.plist is set to the AppIcon source. The Info.plist file is correctly pointing into the root folder for the Assets.xcassets folder. And finally based on other forum posts, I tried adding the Include Image Assets list to .csproj with no luck.
One thing I just realized is that I can completely delete the Assets folder from the root, and Visual studio does not care when it builds.
This is incredibly frustrating. There is zero reason for this so be so difficult. Thank you ahead of time, I am completely lost at this point.
This may be the answer and I am having the exact same issue and have invested many hours in trying to overcome this.
I have created a new Xamarin solution and replaced all Xamarin PNGs with my own in the Asset Catalog and removed ALL the Xamarin images. Still the application and Launch screen display the Xamarin logo. Baffling and frustrating!
I am running the following environment:
Microsoft Visual Studio Enterprise 2019
Version 16.10.4
Xamarin 16.10.000.234 (d16-10#ecaf29b)
Xamarin Designer 16.10.0.115 (remotes/origin/c750fbf1bde3c720d077f51640fe197c6dac7cbe#c750fbf1b)
Xamarin Templates 16.10.5 (355b57a)
Xamarin.Android SDK 11.3.0.4 (d16-10/ae14caf)
Xamarin.Android Reference Assemblies and MSBuild support.
Mono: b4a3858
Java.Interop: xamarin/java.interop/d16-10#f39db25
ProGuard: Guardsquare/proguard/v7.0.1#912d149
SQLite: xamarin/sqlite/3.35.4#85460d3
Xamarin.Android Tools: xamarin/xamarin-android-tools/d16-10#c5732a0
Xamarin.iOS and Xamarin.Mac SDK 14.20.0.24 (c4b89cddb)
Xamarin.iOS and Xamarin.Mac Reference Assemblies and MSBuild support.
I am testing on an iPhone 7 Plus with iOS 14.7.1 and using the following default Nuget packages:
NETStandard.Library 2.0.3
Xamarin.Essentials 1.6.1
Xamarin.Forms 5.0.0.2012
Where is the Xamarin icon/logo coming from?
UPDATE: I found that the launch icons are coming from the Hot Restart feature of Visual Studio. I found the launch icon images in %HOMEPATH%\AppData\Local\Temp\Xamarin\HotRestart<version><code><project> folder. See https://learn.microsoft.com/en-us/xamarin/xamarin-forms/deploy-test/hot-restart for details. From the page:
Limitations
Only iOS apps built with Xamarin.Forms and iOS devices are currently
supported.
Only 64-bit iOS devices are supported. As of iOS 11, Apple no longer
allows running iOS apps on the 32-bit architecture (devices earlier
than iPhone 5s).
Storyboard and XIB files are not supported and the app may crash if
it attempts to load these at runtime. Use the HOTRESTART preprocessor
symbol to prevent this code from executing.
Static iOS libraries and frameworks are not supported and you may see
runtime errors or crashes if your app attempts to load these. Use the
HOTRESTART preprocessor symbol to prevent this code from executing.
Dynamic iOS libraries are supported.
You cannot use Xamarin Hot Restart to create app bundles for publishing. You will still need a Mac machine to do a full
compilation, signing, and deployment for your application to
production.
Asset Catalogs are currently not supported. When using Hot Restart, your app will show the default icon and launch screen for Xamarin
apps. When paired to a Mac, or developing on a Mac, your Asset
Catalogs will work.

I lost all the iOS simulators in Appcelerator Studio? How do I get them back?

I haven't been able to build to my iPhone 6 so yesterday I was advised to add to Xcode (in Preferences > Accounts tab) the Apple ID of the leader of our informal team.
Still wasn't able to build to my iPhone, and today I realized that all my iOS simulators have disappeared from Appcelerator Studio.
What did I do to disappear them from this project? And how do I restore them? (I see that they're still there in another project.)
I had the same problem and found the answer here.
1.Go to Home(jacklee).
2.Go to Folder and find the titanium folder (.titanium).
3.find the files calling "config.json" and Edit the files.
4.change the ""selected": "3.5.1.GA"" to the Latest SDK (any GA Version should be fine).
5.Delete the RC(beta)SDK.
Problem might be with your deployment target selection in the tiapp.xml file, make sure you select 'iPhone' checkbox in the tiapp.xml editor of your project.

Building iOS App does not update on iPhone or Simulator

I am trying to get an iOS project started with Xamarin.iOS for Visual Studio linked to a Mac build host and connected iPhone.
I have started dummy projects in Visual Studio on my PC, Xamarin Studio on the Mac, and XCode 7 on the Mac. They all share this problem.
I have tried running the build on both the physical iPhone and a Simulator on the Mac. The problem persists for both despite all my efforts.
The problem is this: The first version ever built of the test app is the one that runs. If I make ANY changes and rebuild, those changes will NEVER be reflected in the app running on the phone or simulator. It will ALWAYS run the first build I ever made, and the debugger refuses to attach.
I have tried deleting the app from the phone between builds. I have tried deleting all bin and obj files from all projects in the Visual Studio solution between builds. If I could find any similar files on the Mac for Xamarin Studio, XCode, or the Xamarin Mac Build host, I would delete them too, but I'm unfamiliar with the build process or file system of a Mac. Still, this is a problem that shouldn't be happening Regardless.
I have even tried restarting Visual Studio. I would have tried restarting the other parts of my setup (the Xamarin Build Host, Xamarin Studio, XCode, the iPhone, and the iPhone Simulator), but decided not to bother, since restarting components between every build is unacceptable and not a solution.
All searches I do on the web only bring up topics related to Apple Provisioning for test deployment. Nothing useful. Very frustrating. Does anyone have any idea what might be going on here?
Edit: Correction. Changes made in Xamarin Studio on the Mac are reflected on build/run, but not from Visual Studio on the PC linked via Build Host, or from XCode.
Also note: All 3 test apps use the same app identity in their plist files ("com.somecompany.-"). And when building in one environment (say Visual Studio) it WILL overwrite the version from the last environment used (say XCode), but it will still use the first version ever made in the environment being built from.
So for example, if the main page on the Visual Studio project has a label saying "This is the VS version.", and the XCode project label says "This is the XCode version.", I can build/debug in either one, and the label will say the expected thing on the phone.
But if I change those labels in some way, like by adding " duh..." to the end of them so they say "This is the VS version. duh..." and "This is the Xcode version. duh...", no matter how many times I build and run in either environment, the app will still just say "This is the VS version." or "This is the XCode version."
Partially solved. (Solved for Visual Studio with Build Host, not for XCode)
In Visual Studio, the test project is a Xamarin.Forms solution, meaning that it consists of a library project--"TestApp (Portable)"--and other projects for each platform it should build for--"TestApp.iOS", "TestApp.Driod", etc.
By right clicking on the solution and bringing up its properties, then going to Configuration Properties -> Configuration, I was able to see that the library project was not set to build for some reason. So the iOS project would build, and everything would LOOK like the compiler was doing it's job, but the iOS project was still building off the non-rebuilt library.
After checking the box for "Build" on the TestApp library project and applying, everything worked. The debugger even attaches again.
Unfortunately, XCode still remains an unintuitive and mysteriously useless piece of scrap. Answers regarding its behavior on this matter would still be appreciated.

Xcode 6.4: OS X and iOS Targets, Cordova

So I just installed Xcode 6.4 to start some development on my new Mac, and after creating an empty iOS project, I see the message "No OS X or iOS Targets Found". I also see a message under my project folder: "base SDK missing. But I was under the impression a normal install of Xcode also installs all basic SDKs required for Mac and iOS development?
It seems there is absolutely no information on this message on the web. I think it is not an error per-se, more like I need to create or import some build targets, but can anyone explain what I need to do to get my project built and running?
I also need to use XCode with Cordova (or PhoneGap), but there does not seem to be any clear information on how to get XCode properly set up for that. Any pointers for this would be appreciated.
I haven't created an empty project in a long time so can't really comment on the empty project. But to make your life MUCH simpler, I would use one of the default templates and go from there. The simplest is probably the "Single View application".
Admittedly, this does not solve the issue, but it will get you going (which I assume is really what you want to do).
Go to the Project menu, then Edit Project Settings. Select the Build tab, and near the top, there is a Base SDK setting.
Choose the latest iOS.
You might need to clean the project or restart Xcode.

Xcode iOS Base SDK Missing

I have an old iOS app that I never distributed and am now trying to work on the project again. It worked fine with an earlier version of Xcode but I was not ready to deploy it at that time. Now I am using the current version of Xcode but I have an error that there is a missing base SDK. I have explored every posting here with that error message and they did not work for me.
On investigation in Xcode. I can choose my app under "Project" pane. With the Info tab chosen, it has under Deployment Target as "Mac OS X Deployment Target" and Default in the drop list.
This is an iOS app and not a Mac OS X app. How do I change this?
I already have the base SDK as the Latest iOS.
Suggestions?
Try this:
Open Xcode and Press cmd + 1
In left panel choose your project -> Your target in center panel-> Build Settings in right panel
Find "Base SDK" and choose "Latest iOS". If you see a Release and Debug lines, then choose this for both Release and Debug.
Restart your Xcode
Usually when you see this, it's when you've got an old iOS project and you're using a version of Xcode that uses a newer base iOS. In those cases, you can click on the target on the top of the tree structure of the Project Navigator on the left, and you'll see the project settings. There's a button labelled "Validate Settings" and will show up near the lower center portion of the main panel. Click on it.
If that doesn't do it (e.g. it's from a really old version and Xcode can't figure out how to remedy it), it might be easier to recreate the project. Create a new iOS project and then copy your source code, its NIBs and resources into that project. Maybe that will be easier than trying to fix the old project you have.

Resources