Mac OS 10.8.2. Used Homebrew to install FreeRDP FreeRDP version 1.0.1. I have tried several different methods of shell launching a program in FreeRDP. It does not work for me. I have tried using remote app which closes immediately after opening. I have tried using the -s, and -c variables. This is a Mac connecting to a Windows 7 machine. Jul 04, 2013 I just recently got a macbook pro and I decided to buy my first app from the Mac App Store yesterday. When I bought it, it didn't seem to load and it went straight to the Launchpad like it was trying to install. The app then disappeared and a message popped up saying: 'The application could not be downloaded. The installation could not be started.' Nov 27, 2009 Although I don't care for MS Word or MS Office, what I'd like to see is a re-issue of the old 'Microsoft Works' app, for OS X. MS Works was clean, simple, and quick. I still use a 1993 version of it on my g4, running under Classic, to manage databases and a few spreadsheets. Nov 15, 2019 With macOS Catalina, your iTunes media library is now available in the Apple Music app, Apple TV app, Apple Books app, and Apple Podcasts app. And Finder is where you can manage and sync content on your iPhone, iPad, and iPod touch.
- App Does Not Exist Machine
- App Does Not Exist Macbook Pro
- App Does Not Exist Mac Download
- App Does Not Exist Machines
If an app isn't working as you expect
After you upgrade macOS, you might find that some third-party apps don't work or act as you expect. An app might not open, run, or install, even if you try to reinstall it.
You might see this issue if:
- Your Mac has software installed on it that's known to be incompatible with your new macOS version. This software is placed in an Incompatible Software folder during the upgrade process.
- Your Mac has software installed on it that conflicts with updates to System Integrity Protection in macOS High Sierra.
Make sure that you have the latest version
If an app doesn’t work after you upgrade, make sure that you have the latest version:
- Check for an updated version of the app that is compatible with your new OS. Apps in the Mac App Store list their compatibility and system requirements on their product pages.
- Find out whether the app developer has a new version or plans to release a new version of the app that is compatible with your new OS.
Xamarin.iOS cannot resolve System.ValueTuple
This error occurs due to an incompatibility with Visual Studio.
- Visual Studio 2017 Update 1 (version 15.1 or older) is only compatible with System.ValueTuple NuGet 4.3.0 (or older).
- Visual Studio 2017 Update 2 (version 15.2 or newer) is only compatible with the System.ValueTuple NuGet 4.3.1 or newer .
Please choose the correct System.ValueTuple NuGet that corresponds with your Visual Studio 2017 installation.
Receiving 'Error Retrieving Update Information' Error Message
When attempting to update the software and this error message appears, please try restarting your IDE and logging out and then back in to your account in the IDE.
How do I create outlets or actions with Interface Builder?
With the Introduction of the Xamarin Designer for iOS in Visual Studio for Mac and Visual studio, Xamarin.iOS developers can now take advantage of creating a UI through Storyboards and .xibs. Refer to the Hello, iOS guides for more information on using the designer.
You can also refer to Apple's Outlet and Actions guides for more information on using Outlets and Actions in IB.
System.Text.Encoding.GetEncoding throws NotSupportedException
You may be using an encoding that is not added by default. Checkthe Internationalization pageto learn how to add support for more encoding.
System.MissingMethodException (anything else)
The member was likely removed by the linker, and thus doesn't exist in theassembly at runtime. There are several solutions to this:
- Add the
[Preserve]
attribute to the member. This will prevent the linker from removing it. - When invoking mtouch, use the -nolink or -linksdkonly options:
- -nolink disables all linking.
- -linksdkonly will only link Xamarin.iOS-provided assemblies, such as xamarin.ios.dll, while preserving all types in user-created assemblies (ie. your app projects).
Note that assemblies are linked so that the resulting executable is smaller;thus, disabling linking may result in a larger executable than is desirable.
You are getting a ModelNotImplementedException
If you are getting this exception this means that you are calling base.Method() on a class that overrides a Model. You do not need to call the base method ina class for models (these are classes that are flagged with the [Model]attribute).
This class is not key value coding-compliant for the key XXXX
If you get this error when loading a NIB file it means that the value XXXXwas not found on your managed class. This means that you are missing adeclaration like this:
The above definition is automatically generated by Visual Studio for Mac for any XIBfiles that you add to Visual Studio for Mac in the
NAME_OF_YOUR_XIB_FILE.designer.xib.cs
file.Additionally, the types containing the above code must be a subclass of NSObject. If the containing type is within anamespace, it should also have a [Register] attribute which provides a type name without anamespace (as Interface Builder doesn't support namespaces in types):
Unknown class XXXX in Interface Builder file
This error is generated if you define a class in your interface builder filesbut you do not provide the actual implementation for it in your C# code.
You need to add some code like this:
System.MissingMethodException: No constructor found for Foo.Bar::ctor(System.IntPtr)
This error is produced at runtime when the code tries to instantiate aninstance of the classes that you referenced from your Interface Builderfile. This means that you forgot to add a constructor that takes asingle IntPtr as a parameter.
The constructor with an IntPtr handle is used to bind managed objects withtheir unmanaged representations.
![Machines Machines](/uploads/1/2/6/0/126026076/671693661.png)
To fix this, add the following line of code to the class Foo.Bar:
Type {Foo} does not contain a definition for GetNativeField
and no extension method GetNativeField
of type {Foo} could be found
If you get this error in the designer generated files (*.xib.designer.cs), itmeans one of two things:
1) Missing partial class or base class
The designer-generated partial classes must have corresponding partialclasses in user code that inherit from some subclass of
NSObject
,often UIViewController
. Ensure that you have such a class for thetype that is giving the error.2) Default namespaces changed
The designer files are generated using your project's default namespacesettings. If you have changed these settings, or renamed the project, thegenerated partial classes may no longer be in the same namespace as theiruser-code counterparts.
Namespace settings can be found in the Project Options dialog. The defaultnamespace is found in the General->Main Settings section. If it isblank, the name of your project is used as the default. More advanced namespacesettings can be found in the Source Code->.NET Naming Policiessection.
Warning for actions: The private method 'Foo' is never used. (CS0169)
Actions for interface builder files are connected to the widgets byreflection at runtime, so this warning is expected.
You can use '#pragma warning disable 0169' '#pragma warning enable 0169'around your actions if you want to suppress this warning just for these methods,or add 0169 to the 'Ignore warnings' field in compiler options if you want todisable it for your whole project (not recommended).
mtouch failed with the following message: Cannot open assembly '/path/to/yourproject.exe'
If you see this error message, generally the problem is the absolute path toyour project contains a space. This will be fixed in a future version ofXamarin.iOS, but you can work around the issue by moving the project to a folderwithout spaces.
Your sqlite3 version is old - please upgrade to at least v3.5.0!
This happens when you do all of the following:
- Use Mono.Data.Sqlite
- Use Mac OS X Leopard (10.5)
- Run your app within the simulator.
The problem is that Mono is picking up the OS X
libsqlite3.dylib
, not the iPhoneSimulator's libsqlite3.dylib
file. Your app will work on thedevice, but just not your simulator.Deploy to device fails with System.Exception: AMDeviceInstallApplication returned 3892346901
This error means that the code-signing configuration for yourcertificate/bundle id does not match the provisioning profile installed on yourdevice. Confirm you have the appropriate certificate selected in ProjectOptions->iPhone Bundle Signing, and the correct bundle id specified inProject Options->iPhone Application
Code Completion is not working in Visual Studio for Mac
Ensure that you are using the latest version of Visual Studio for Mac and Xamarin.iOS
If the issue is still present, please file a bug, attaching the ~/Library/Logs/XamarinStudio-{VERSION}/Ide-{TIMESTAMP}.log, AndroidTools-{TIMESTAMP}.log, and Components-{TIMESTAMP}.log log files.
If all else fails, you can try removing the code completion cache so that itis regenerated:
[rm -r ~/.config/XamarinStudio-{VERSION}/CodeCompletionData]
Be careful that you type this command correctly or you could accidentallyremove important files.
Visual Studio for Mac crashes when you copy text
The popular Mac utilities QuickSilver, Google Toolbar and LaunchBar haveclipboard features that corrupt Visual Studio for Mac's memory. In their options, you canlist Visual Studio for Mac as a process they should not interfere with.
Visual Studio for Mac complains about Mono 2.4 required
If you updated Visual Studio for Mac due to a recent update, and when you try to startit again it complains about Mono 2.4 not being present, all you have to do is upgrade your Mono 2.4 installation.
Mono 2.4.2.3_6 fixes some important problems that prevented Visual Studio for Mac fromrunning reliably, sometimes hung Visual Studio for Mac at startup or prevented the codecompletion database from being generated.
Once you install the new Mono, Visual Studio for Mac will start as expected.
Assertion at ../../../../mono/metadata/generic-sharing.c:704, condition `oti' not met
If you are receiving the following stack trace:
It means that you are linking a static library compiled with thumb code intoyour project. As of iPhone SDK release 3.1 (or higher at the time of thiswriting) Apple introduced a bug in their linker when linking non-Thumb code(Xamarin.iOS) with Thumb code (your static library).You will need to linkwith a non-Thumb version of your static library to mitigate this issue.
System.ExecutionEngineException: Attempting to JIT compile method (wrapper managed-to-managed) Foo[]:System.Collections.Generic.ICollection`1.get_Count ()
The [] suffix indicates that you or the class library are calling a method onan array through a generic collection, such as IEnumerable<>,ICollection<> or IList<>. As a workaround, you can explicitly forcethe AOT compiler to include such method by calling the method yourself, and bymaking sure that this code is executed before the call that triggered theexception. In this case, you could write:
Which will force the AOT compiler to include the get_Count method.
Visual Studio for Mac source editor is extremely slow
Sometimes the Visual Studio for Mac source editor becomes extremely slow, appearing tohang for several seconds between typing characters.
This issue is very rare and extremely hard to reproduce - it usually cannotbe reproduced on the same machine after restarting Visual Studio for Mac. For this reasonwe would appreciate it if you could perform several debugging steps beforerestarting Visual Studio for Mac, and send the results to us.
- Try closing the editor tab, and re-opening it. Does it take a little bit of editing or moving the caret around until the slowdown happens again?
- Disable 'Beam Sync' using the 'Quartz Debug' developer tool (which you can find using Spotlight), and check whether the source editor performance is restored to normal.
- Try repeating step (1) with Beam Sync still disabled.
- If the editor hangs for more than a few seconds, try to run 'killall -QUIT [Visual Studio for Mac]' in a terminal while it is hung. It may be difficult to time the kill command to happen while the editor is hung, but it's essential to do so, because the command forces Mono to write stack traces of all threads to the MD log, which we can use to discover what state the threads are in while the XS is hung.
Please attach the XS logs, ~/Library/Logs/XamarinStudio-{VERSION}/Ide-{TIMESTAMP}.log, AndroidTools-{TIMESTAMP}.log, and Components-{TIMESTAMP}.log(in older versions of XS/MonoDevelop, just send ~/Library/Logs/MonoDevelop-(3.0|2.8|2.6)/MonoDevelop.log).
Compiled application is very large
To support debugging, debug builds contain additional code. Projectsbuilt in release mode are a fraction of the size.
As of Xamarin.iOS 1.3 the debug builds included debugging support for everysingle component of Mono (every method in every class of theframeworks).
With Xamarin.iOS 1.4 we will introduce a finer grained method for debugging,the default will be to only provide debugging instrumentation for your code andyour libraries, and not do this for all of the Mono assemblies (this will still bepossible, but you will have to opt-in to debugging those assemblies).
Installation Hangs
Both Mono and Xamarin.iOS installers hang if you have the iPhone Simulatorrunning. This problem is not limited to Mono or Xamarin.iOS, this is aconsistent problem across any software that tries to install software on MacOSSnow Leopard if the iPhone Simulator is running at installation time.
Make sure you quit the iPhone simulator and retry the installation.
Debugger is unable to connect with the device
When you start debugging a device configuration, you will see the debuggershow a dialog indicating that it is trying to connect to the application. Thereare several reasons the debugger may not be able to connect to the application,depending on the mode you're using to connect (USB or WiFi).
If the device and the debugger host are on different networks, a firewall or private network may be preventing theapplication from connecting to the debugger host in WiFi mode.
Visual Studio for Mac may not be able to query the correct IP of the host. In WiFi mode Visual Studio for Mac gives the application all the IPsit can find of the host, and the application tries them all to see if it can useany of them to connect to Visual Studio for Mac.
App Does Not Exist Machine
Another device is connected to a USB port on the host. In afew cases other devices connected to the USB ports on the host have been knownto somehow interfere with debugging in USB mode.
If either WiFi or USB mode does not work, you can easily try the other: inVisual Studio for Mac, open the Preferences, go to the Preferences/Debugger/iPhoneDebugger page, and toggle the 'Debug iOS devices over WiFi instead of over USB'checkbox. If neither works, you can see more information about thefailure in the device console in verbose mode (which is enabled by adding '-v-v -v' to the additional mtouch arguments in the project's options).
Error 134: mtouch failed with the following message:
This error could be raised if you are trying to build with -nolink on theXamarin.iOS 1.4 style of releases. You can work around this error byspecifying Extra Arguments in your monodevelop project configuration.
Add the argument
-nosymbolstrip
and the problem should be resolved.
Distribution identity is not shown in Visual Studio for Mac project signing options
![Machines Machines](/uploads/1/2/6/0/126026076/713866049.png)
Visual Studio for Mac 2.2 has a bug that causes it not to detect distributioncertificates that contain a comma. Please update to Visual Studio for Mac 2.2.1.
Error 'AFCFileRefWrite returned: 1' during upload
While uploading an app to your device you may receive an Error'AFCFileRefWrite returned: 1'. This can happen if you have a zero-lengthfile.
Error 'mtouch failed with no output'
The current release of Xamarin.iOS and Visual Studio for Mac fail when the project nameor the directory where the solution or project are stored contain spaces.To fix this:
- Make sure that neither your project or the directory where it is stored contains a space.
- In your project 'Main Settings' make sure that the Project Name does not contain any spaces.
Error 'The binary you uploaded was invalid. A pre-release beta version of the SDK was used to build the application'
This error is usually caused with a project that was started in iPaddevelopment before Xamarin.iOS 2.0.0 was released, you likely have some keys inyour Info.plist like:
This keypair should be removed as Visual Studio for Mac handles it for youautomatically.
Error 'A pre-release beta version of the SDK was used to build the app'
(Contributed by Ed Anuff)
Follow these steps:
- Change the SDK version in iPhone Build to 3.2 or iTunes connect will reject it on upload because it is seeing an iPad compatible app built using an SDK version less than 3.2
- Create a custom Info.plist for the project and explicitly set MinimumOSVersion to 3.0 in it. This will override the MinimumOSVersion 3.2 value set by Xamarin.iOS. If you do not do this, the app will not be able to run on an iPhone.
- Rebuild, zip and upload to iTunes connect.
Unhandled Exception: System.Exception: Failed to find selector someSelector: on {type}
This exception is caused by one of three things:
- You have provided a Selector to the Objective-C runtime without applying the corresponding [Export] attribute to a method
- You have enabled full linking and not applied the [Preserve] attribute to the [Export]ed method.
- You have applied the [Export] attribute to a private method in an inherited type.
MainWindow.xib.designer.cs file is not updated
There was a bug in Xamarin Studio 2.4 that caused it not to group theMainWindow.xib file with the MainWindow.xib.designer file in new projects. Thismeant it would not update the designer code for that particular file.
This issue is fixed in the version of Visual Studio for Mac that's available in itsbuilt-in updater, so please ensure you use the newer version.
You can fix existing projects by removing (not deleting) the xib and itsdesigner file, then adding it back. This should re-group the filescorrectly.
UIAlertView or UIActionSheet vanish after being created
App Does Not Exist Macbook Pro
If you have some code like this:
the 'actionSheet' object lives as a temporary variable in the function and assoon as the function terminates, the object is eligible for garbage collection,so it ends up being garbage collected.
To fix this problem, you need to keep a reference to 'actionSheet' outsideyour method, somewhere that will live beyond your method.
Project Always Runs in the iPad Simulator
The iPhone SDK 4.0 installer installs 2 SDKs - the 3.2 SDK, for buildingiPad-only apps, and the 4.0 SDK, used for building iPhone and Universal apps. Italso installs a 3.2 simulator, which simulates only an iPad, and a 4.0 simulatorthat simulates iPhone or iPhone 4. All older SDKs and simulators areremoved.
Visual Studio for Mac iPhone project build options include a setting for the SDKversion that will be used in building your app. This setting can be found in Project Options->Build->iPhone Build.
New projects in Visual Studio for Mac use the oldest installed SDK as their default SDKsetting, and if the SDK specified does not exist, Visual Studio for Mac will use theclosest it can find to build your app. This was done so that projectswould not always require the newest SDK. However, this currently results in the3.2 SDK being used - which results in the iPad simulator being used.
To fix this by using the 4.0 SDK, go to ProjectOptions->Build->iPhone Build> and change the SDK value to '4.0' usingthe dropdown box. You must do this for each configuration and platformcombination, accessed using the dropdowns at the top of the panel.
The SDK version should not be confused with the 'Minimum OS version' setting.This value does not have to match the SDK version value - it affects the minimumversion of the OS your app will install on, which can be older than the SDK, aslong as you use only APIs that exist in the older OS, or guard use of newerfeatures using runtime OS version checks. You should set it to the oldest OSversion on which you test your app.
Note also that the Project->iPhone Simulator Target> menu can beused to pick the simulator that is used by default when running/debugging aproject. Additionally, the Run->Run With> menu can be used to pick aspecific simulator with which to run
ibtool returns error 133
This means that you have XCode 4 installed. In XCode 4, the toolibtool was removed, it is no longer possible to edit your XIB files with astandalone tool.
If you want to use Interface Builder, install XCode series 3, available from Apple's web site.
'Can't create display binding for mime type: application/vnd.apple-interface-builder'
This error happens if you try to create an iPhone UI from a non-iPhoneproject. Make sure that you start with an iPhone/iPad solution, it is notpossible to just add iPhone UI elements to a non-iPhone/iPad project.
Startup crash when executing inside the iOS simulator
App Does Not Exist Mac Download
If you get a runtime crash (SIGSEGV) inside the simulator along with a stacktrace that looks like this:
...then you probably have one (or more) stale assembly in your simulatorapplication directory. Such assemblies may exists since Apple iOS simulatoradds and updates files but never deletes them. If this happens then the easiestsolution is to select 'Reset and Content and Settings...' from the simulatormenu.
Warning
This will remove all files, applicationsand data from the simulator. Next time you execute your application,Visual Studio for Mac will deploy it into the simulator and there will be no old, staleassembly to cause the crash.
Simulator hangs during application installation
This can happen when application names include a '.' (dot) in their name.This is forbidden as the executable name in CFBundleExecutable - even if it canworks in many other cases (like devices).
'The value should not include any extension on the name.'
Error: 'Custom attribute type 0x43 is not supported' when double clicking .xib files
This is caused by attempting to open .xib files when environment variablesare set incorrectly. This should not happen with normal usage ofVisual Studio for Mac/Xamarin.iOS, and re-opening Visual Studio for Mac from /Applications should fixthe problem.
When attempting to update the software and this error message appears, please e-mail *[email protected]*
Application runs on simulator but fails on device
This issue can manifest in several forms, and doesn't always produce a consistent error. If the application contains a .xib, check to make sure the Build Action on the .xib is set to InterfaceDefinition. This is the default build action for .xibs.
To check the build action, right click on the .xib file and choose Build Action.
App Does Not Exist Machines
System.NotSupportedException: No data is available for encoding 437
When including 3rd party libraries in your Xamarin.iOS app, you might get an error in the form 'System.NotSupportedException: No data is available for encoding 437' when trying to compile and run the app. For example, libraries, such as
Ionic.Zip.ZipFile
, may throw this exception during operation.This can be solved by opening the options for the Xamarin.iOS project, going to iOS Build > Internationalization and checking the West internationalization.
Could not launch Xamarin.Launcher Could not find the executable 'mlaunch.exe'
In some cases anti-virus software can incorrectly flag the Xamarin.iOS SDK as malware and remove required files, corrupting the SDK. This will result in errors such as 'Could not launch Xamarin.Launcher Could not find the executable 'mlaunch.exe'.
If you have been affected, exclude mlaunch.exe from your antivirus scanner to prevent re-occurrence. For more information, see How to create an application exception in the Symantex Endpoint Protection Manager for Symantec, and Exclude files and folders from Norton Auto-Protect, SONAR, and Download Intelligence scans for Norton. In addition, consider reporting a false positive to Symantec or Norton.
Important
For Norton users, community members have also reported that you may need to disable idle scan as discussed here: Windows, Mac.
Once you have added an exclusion for mlaunch.exe, a re-installation will be required to restore the missing files. The simplest approach to do this is to switch channels in the updater:
- Visual Studio menu > Check for updates.
- Select a different update channel in the dropdown and press the Switch channel button.
- Wait for updates to download.
- Switch back to original channel and install updates.
If these instructions don't resolve your issue, please add a comment to the following GitHub issue: 8736.