Skip to main content
Version: 6.0.0

Initialize Finotes

You need to call the Initialize function in your appDelegate didFinishLaunchingWithOptions:

AppDelegate:

#import <FinotesCore/Fn.h>

- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions {

[Fn initialize:application];
}

Testing Integration

Now that the basic integration of Finotes framework is complete, let us make sure that the dashboard and framework are in sync.

Step One - Add Test API.

Add test API after Initialize call.

AppDelegate:

#import <FinotesCore/Fn.h>

- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions {

[Fn initialize:application];

[Fn test];
}

Step Two - Run the app

Now run the application in a simulator or real iOS device (with an active network connection).

M1 (arm64) Simulator.

In case you are running arm64 based simulator in a M1 macs, please make sure to follow the steps to resolve the following error.
error building for iOS Simulator, but linking in object file built for iOS, for architecture arm64.

  1. Go to Targets section, select each target and do the following:
  2. Set Build Active Architecture Only to YES
  3. Add Excluded Architectures and set its value to arm64 (See attached)
  4. Set Active scheme (on toolbar next to project name) to any iOS Simulator
  5. Clean Build folder from Product Menu and build.

Step Three - Finally

Once the application opens up, open Finotes dash..

The test issue that we raised should be reported.

In case the issue is not listed, make sure the right app and platform is selected at the top of the dashboard. If the issue is still not synced in Finotes dashboard, Click Here.

Make sure to remove the test API, else every time the app is run, a test issue will be reported.

Framework supports offline caching of issues that are failed to sync. Check out the Offline Caching section for details.

Now, Framework will report all memory leaks, abnormal memory usages, App Hangs, frame rate issues and crashes (crash reporting will be activated only in release builds) if they occur in your application.