iFakeLocation VS xamarin-macios

I then run this program through my iPhone plugged into my computer (iOS only, there are android ones) - https://github.com/master131/iFakeLocation

This is an easy way to spoof your location on your phone with your computer. You just need to plug in your phone to change the location. After you change the location you can unplug your phone

this is better than anything people recommended i’d say. it’s free and open source and it doesn’t contain malware like 3u.

How to install You first have to enable “Developer” toggle in settings. There are several ways to do this. By Xcode on Mac (which I didn’t use cause I don’t own one) or by using GPS faking tools such as this: https://github.com/master131/iFakeLocation/releases

Or https://github.com/master131/iFakeLocation

iFakeLocation (github.com), 3utools(3u.com). I’ve been using this one and has worked flawlessly.

https://projectzerothree.info combined with https://github.com/master131/iFakeLocation and the 7/11 fuel price lock is what I use.

iFakeLocation - https://github.com/master131/iFakeLocation - great for apps that normally detect jailbreak eg 711.

I use this to https://github.com/master131/iFakeLocation fake my location and lock in the cheapest 7-11 fuel in Australia, usually save like $10 every time I fuel up

Xamarin.ios y Xamarin.Mac: Licencia MIT.

Try to build the project for Android and iOS respectively. If you suffered from the iOS build issue Error MT4109: Failed to compile the generated registrar code caused by Xcode 14, you can visit https://github.com/xamarin/xamarin-macios/issues/15954 to find the solution. The issue can be fixed by installing xamarin.ios-16.0.0.72.pkg. To run the app on iOS 16, turn on Settings > Privacy & Security > Developer Mode.

See this for more info.

There is nothing planned. Downgrade immediately https://github.com/xamarin/xamarin-macios/issues/15954

MAUI on iOS and MacCatalyst use: https://github.com/xamarin/xamarin-macios

You can see in old issues like this how uncertain even the core team was about it. It's not really tenable to fly that blind.

I think they're still doing tooling updates for Xamarin for a while. For one, there are platforms that for now aren't (yet) moving to .NET 6 at all, such as watchOS. And second, they seem to have changed their Apple platforms tooling to basically dual-target Mono (for Xamarin) and .NET 6 (for MAUI).

Microsoft decided not to support the Apple Watch in .NET 6 (https://github.com/xamarin/xamarin-macios/issues/8955), which made me uncertain as to its future on the Apple Watch - I was also interested in learning Swift and SwiftUI.