testfairy_flutter 3.0.0

TestFairy integration for Flutter, bundled with the native SDK

TestFairy Flutter Integration

This is TestFairy integration for Flutter, bundled with the native SDK.

Installation

Read installation docs at pub.dartlang.org

Quick Start

Include the library and run your main app like this.

Make sure your project is AndroidX compatible.

Minimum supported iOS target is 11.0.

# inside pubspec.yaml

dependencies:
  testfairy_flutter: any

// inside your main.dart

// @dart = 2.18 
// You can use other dart versions but we suggest 2.12 for better compile time checks.
import 'dart:async';
import 'dart:io';
import 'package:testfairy_flutter/testfairy_flutter.dart';

void main() {
  HttpOverrides.global = TestFairy.httpOverrides();

  runZonedGuarded(
    () async {
      try {
        FlutterError.onError =
            (details) => TestFairy.logError(details.exception);

        // Call `await TestFairy.begin()` or any other setup code here.

        runApp(TestFairyGestureDetector(child: TestfairyExampleApp()));
      } catch (error) {
        TestFairy.logError(error);
      }
    },
    (e, s) {
      TestFairy.logError(e);
    },
    zoneSpecification: new ZoneSpecification(
      print: (self, parent, zone, message) {
        TestFairy.log(message);
      },
    )
  );
}

How to compile with latest Flutter and null-safe Dart?

In order to use TestFairy with the latest stable Flutter channel, you must set the minimum version for the plugin as 2.1.0.

In order to use TestFairy with the latest unstable Flutter channel, you must clone this repo and use it as an offline dependency instead of the published version in pub.

1. Clone this repo.

2. Use the following code to include the clone as an offline dependency (assuming both projects reside in the same directory as siblings).

dependencies:
  testfairy_flutter:
    path: ../testfairy-flutter # or "./testfairy-flutter" if you cloned it inside your main project as a child directory 

3. Checkout testfairy-flutter to your VCS without including its .git directory.

4. When there is a new update in this repo, delete testfairy-flutter and retry the steps.

Troubleshoot

• I see warning: None of the architectures in ARCHS (x86_64) are valid when I build and iOS app.

Launch your Runner workspace and add x86_64 to VALID_ARCHS under Build Settings.

• I see Specs satisfying the TestFairy dependency were found, but they required a higher minimum deployment target. when I build and iOS app.

You have to update the native SDK alongside with CocoaPods repository.

Run pod repo update and update the plugin in pubspec.yaml. Then run cd ios; pod update TestFairy; cd ...

• I have my own HttpOverrides.global setup. How can I make it work with TestFairy?

Copy this file to your project. Add the necessary functionality and assign to HttpOverrides.global an instance from your new implementation.

• I see Errno::ENOENT - No such file or directory @ rb_sysopen - ./ios/Pods/Local Podspecs/testfairy.podspec.json when I build an iOS app.

This happens due to a pod misconfiguration bug on the Flutter side. We have a blog post explaining the fix.

Clean your project, remove ios/Podfile and Xcode workspace file entirely. (make sure you have backups just in case)

flutter clean
rm -rf ios/Podfile ios/Podfile.lock pubspec.lock ios/Pods ios/Runner.xcworkspace

Revert to cocoapods 1.7.5 temporarily.

gem uninstall cocoapods
gem install cocoapods -v 1.7.5

Add the following line to the beginning of your iOS project's generated Podfile.

# Beginning of file
use_frameworks!

# The rest of the file contents
# ...

Install pods.

pod repo update
cd ios
pod install
cd ..

Retry your build.

Once your build is successful, you can update cocoapods back to its latest version. If the error reoccurs, you will have to revert back to 1.7.5 and retry the steps.

• I see Automatically assigning platform ios with version X.Y when I build.

TestFairy supports iOS 11.0 and above. Please change the build target accordingly in your Xcode project.

• I see Looks like TestFairy has an upgrade to do... 1.X.Y+hotfixZ is the latest stable branch or errors related to Jetifier in the logs when I call an SDK method.

Migrate your Android project to AndroidX by following this guide.

• I see Undefined symbols for architecture error during compilation.

You must use frameworks and specify a platform version of at least 11.0 in your generated iOS project's Podfile. Please make the following changes in ios/Podfile and rebuild.

target 'Runner' do
  platform :ios, '11.0'   ####################################### <--- add this and specify at least 11.0

  use_frameworks!        ####################################### <--- add this, and try building if there is 
                         #######################################      no Swift code or plugin in the project.
                         #######################################      If there is Swift code, please also add 
                         #######################################      the marked line below

  ...
end

post_install do |installer|
  installer.pods_project.targets.each do |target|
    target.build_configurations.each do |config|
      config.build_settings['ENABLE_BITCODE'] = 'NO'
      config.build_settings['SWIFT_VERSION'] = '3.2'  ########## <--- add this, change the version to what's being
                                                      ##########      used in the project, remove if there is none
    end
  end
end

• CocoaPods could not find compatible versions for pod "TestFairy".

This is an old bug in the plugin pubspec file. First, run flutter clean in your root directory.

Please move ios/Podfile.lock into a temporary place before running pod repo update; pod install in your ios directory.

If some of the libraries you use need to be at specific versions, copy the necessary lines from your backed up Podfile.lock into the newly created one. Please keep the lines related to TestFairy (note the title case in the name) untouched.

Finally, run pod repo update; pod install; pod update TestFairy again to re-download libraries from the replaced lines.

If everything went smoothly, this issue should never happen again.

• There are syntax errors in TestFairyFlutterPlugin.java or TestFairyFlutterPlugin.m file.

In your project root, run flutter clean; cd ios; pod repo update; pod install; pod update TestFairy; cd .. and test again.

Docs

Go to docs...

Credits

• This library incorporates code pieces derived from @leishuai's flutter_widget_detector library.
• Special thanks to @Peterkrol12 for the contribution for Flutter 3 support.