iOS10

If it's urgent and you don't need to test things on Flipper, try to remove all references to Flipper in iOS side.

It would be commenting this part in AppDelegate.m

Make sure that your project's minimum deployment target (the one that referenced in your Podfile) is at least iOS 9 (see Firebase/Crashlytics release notes)

Unfortunately when cocoapods initially create the Podfile, doesn't take into account your projects minimum deployment target. Instead adds a default value in a comment.

The first time that you run pod install you will get a warning about not specified minimum deployment target. Also cocoapods documentation doesn't mention anything regarding this behavior.

So, you have to have to manually edit your Podfile and add something like this:

Yes, I also got into this after upgrading to ios 14. So, first, add this to you podfile:

The razor pay pod is not compatible with Xcode 12.

The razor pay pod v1.1.9 is in pre-release(See below image) which is Xcode 12 complied version.

What you can do is just update the razor pay pod version to 1.1.7 to 1.1.9 and give it a try.

Or you can use razor pay pod v1.1.8(stable release) in lower than Xcode 12 version and when v1.1.9 is available you can move it Xcode 12.

You can do the following to use v1.1.9...

• Comment the razor pay pod from pod file.

You can't schedule a notification that repeats daily. That notification would happen only once, and then you would have to schedule it again, which means that you would have to open the app again.

There is BGTask API introduces in iOS 13, that can be used to perform some background tasks, but not this one, you can not schedule the task for specific time.This API last only works when app is in the background, not when it is killed. You can only set some time interval that the system will use as a guiding point to determine when to perform you app's code. But in my experience it is pretty unreliable.

The only way to achieve this is to implement remote push notifications. Push notifications also work even when the app is killed.

I had the same issue. Have a look at the two files

CommonLib/Config/GREYAppState.m


CommonLib/GREYLogger.m

They are currently not part of the project, but they should be. Add them, and make sure that the target membership is for both set to AppFramework. After that, the AppFramework built correctly on my system.

I had this problem too. I couldn't build for the simulator with exactly the same error and also broke my head thinking it was because of CocoaPods, but I was mistaken.
As of Xcode 12 Beta release notes:

"The Build Settings editor no longer includes the Valid Architectures build setting (VALID_ARCHS), and its use is discouraged. Instead, there is a new Excluded Architectures build setting (EXCLUDED_ARCHS). If a project includes VALID_ARCHS, the setting is displayed in the User-Defined section of the Build Settings editor. (15145028)"

I was able to resolve this issue by manually editing the project file (I opened my .xcworkspace with a text editor) and removing all the lines referring to VALID_ARCHS.
After that, I was able to build for the simulator just fine.

I want to implement .net core support now. But I cant use controls like UserControl because the Microsoft.NET.Sdk.WindowsDesktop SDK isn't referenced. The .net framework is easy to implement because I only have to reference each assembly... But in .net core, I can't reference the assembly..

After doing a deep research, I found that Microsoft.NET.Sdk.WindowsDesktop cannot be used by SDKReference.

As a suggestion, you could create a custom targets file and then import it into your PCL-project to use the Net Core SDK.

1) create a file called custom.targets in your PCL project folder.

2) Then add these in custom.targets:

try to change your TargetFrameworks become like this