使用Xamarin绑定启动Optimizely时出错

时间:2015-09-02 06:30:08

标签: ios xamarin xamarin.ios optimizely objective-sharpie

我想使用Optimizely改进App中的A / B测试。为此,我实现了一个等于此repo的Xamarin Binding:

https://github.com/JustGiving/XamarinBindings/tree/master/Optimizely.iOS

当我以这种方式在FinishedLaunching上注册我的API密钥时:

static readonly string OptimizelyAPIToken = "mykey~projectid";

public override bool FinishedLaunching(UIApplication application, NSDictionary launchOptions)
{
      // create a new window instance based on the screen size
      Window = new UIWindow(UIScreen.MainScreen.Bounds);
      root = new WelcomeController();
      nav = new UINavigationController(root);

      // If you have defined a root view controller, set it here:
      Window.RootViewController = nav;

      // make the window visible
      Window.MakeKeyAndVisible();

      OptimizelyiOS.Optimizely.SharedInstance().VerboseLogging = true;

      OptimizelyiOS.Optimizely.StartOptimizelyWithAPIToken(OptimizelyAPIToken, launchOptions ?? new NSDictionary());


      return true;
}

我有这个问题

2015-09-01 11:57:23.588 MyAppOptm[3540:750731] [Optimizely Logging]: (ERROR) NSInvalidArgumentException: Stack Trace:
(
0 CoreFoundation 0x22787fa7 + 150
1 libobjc.A.dylib 0x310fec8b objc_exception_throw + 38
2 CoreFoundation 0x2278d3a9 + 0
3 CoreFoundation 0x2278b15f + 354
4 CoreFoundation 0x226baba8 CF_forwarding_prep_0 + 24
5 MyAppOptm 0x011e32f5 -[Optimizely registerGestureRecognizer] + 176
6 Foundation 0x234c136d __NSFireDelayedPerform + 468
7 CoreFoundation 0x2274dcbf + 14
8 CoreFoundation 0x2274d83b + 650
9 CoreFoundation 0x2274ba8b + 1418
10 CoreFoundation 0x22697f31 CFRunLoopRunSpecific + 476
11 CoreFoundation 0x22697d43 CFRunLoopRunInMode + 106
12 Foundation 0x2340713d + 264
13 MyAppOptm 0x011e24f9 -[Optimizely waitForNetworkWithTimeout:condition:] + 432
14 MyAppOptm 0x011e22af -[Optimizely waitForNetworkWithTimeout] + 274
15 MyAppOptm 0x011e181f -[Optimizely startOptimizelyWithToken:launchOptions:experimentsLoadedCallback:] + 1578
16 MyAppOptm 0x011dd8c1 +[Optimizely startOptimizelyWithAPIToken:launchOptions:experimentsLoadedCallback:] + 164
17 MyAppOptm 0x011dd811 +[Optimizely startOptimizelyWithAPIToken:launchOptions:] + 52
18 MyAppOptm 0x00e8006c wrapper_managed_to_native_ApiDefinition_Messaging_void_objc_msgSend_IntPtr_IntPtr_intptr_intptr_intptr_intptr + 236
19 MyAppOptm 0x00e76b44 OptimizelyiOS_Optimizely_StartOptimizelyWithAPIToken_string_Foundation_NSDictionary + 480
20 MyAppOptm 0x00091ad4 JR_UI_Touch_AppDelegate_FinishedLaunching_UIKit_UIApplication_Foundation_NSDictionary + 2448
21 MyAppOptm 0x00433fdc wrapper_runtime_invoke_object_runtime_invoke_dynamic_intptr_intptr_intptr_intptr + 256
22 MyAppOptm 0x012533f7 mono_jit_runtime_invoke + 1190
23 MyAppOptm 0x0129fd89 mono_runtime_invoke + 88
24 MyAppOptm 0x00ff556d native_to_managed_trampoline_4 + 420
25 MyAppOptm 0x00ffbac5 -[AppDelegate application:didFinishLaunchingWithOptions:] + 100
26 UIKit 0x25e750b3 + 374
27 UIKit 0x2606b929 + 2444
28 UIKit 0x2606dfe9 + 1412
29 UIKit 0x26078c69 + 36
30 UIKit 0x2606c78b + 130
31 FrontBoardServices 0x29328ec9 + 16
32 CoreFoundation 0x2274ddb5 + 12
33 CoreFoundation 0x2274d079 + 216
34 CoreFoundation 0x2274bbb3 + 1714
35 CoreFoundation 0x22697f31 CFRunLoopRunSpecific + 476
36 CoreFoundation 0x22697d43 CFRunLoopRunInMode + 106
37 UIKit 0x25e6ec87 + 558
38 UIKit 0x25e69879 UIApplicationMain + 1440
39 MyAppOptm 0x0022f1f4 wrapper_managed_to_native_UIKit_UIApplication_UIApplicationMain_int_string___intptr_intptr + 272
40 MyAppOptm 0x001aa9d4 UIKit_UIApplication_Main_string___intptr_intptr + 52
41 MyAppOptm 0x001aa994 UIKit_UIApplication_Main_string___string_string + 204
42 MyAppOptm 0x000909c0 JR_UI_Touch_Application_Main_string_ + 172
43 MyAppOptm 0x00433fdc wrapper_runtime_invoke_object_runtime_invoke_dynamic_intptr_intptr_intptr_intptr + 256
44 MyAppOptm 0x012533f7 mono_jit_runtime_invoke + 1190
45 MyAppOptm 0x0129fd89 mono_runtime_invoke + 88
46 MyAppOptm 0x012a34c3 mono_runtime_exec_main + 282
47 MyAppOptm 0x012a3305 mono_runtime_run_main + 476
48 MyAppOptm 0x0123d769 mono_jit_exec + 48
49 MyAppOptm 0x0130a0c8 xamarin_main + 2184
50 MyAppOptm 0x0100c269 main + 112
51 libdyld.dylib 0x316b0aaf + 2
)

我的Optimizely的Info.plist节点是:

        <dict>
            <key>CFBundleURLName</key>
            <string>com.optimizely</string>
            <key>CFBundleURLSchemes</key>
            <array>
                <string>optlyprojectid</string>
            </array>
            <key>CFBundleURLTypes</key>
            <string>Editor</string>
            <key>CFBundleURLIconFile</key>
            <string>Images.xcassets/AppIcons.appiconset/Icon-Small@2x</string>
        </dict>

其中optlyprojectid = optly + projectid(在我的api密钥中)。

1 个答案:

答案 0 :(得分:4)

这可能有所帮助,也可能无效,但Optimizely确实有一个基本的Xamarin绑定 - 我很想知道这是否有帮助:

可以找到绑定文件here

  1. 将SDK中的Optimizely库文件的副本放入与文件Optimizely.linkwith.cs相同的目录中
  2. 该项目现在应该在Xamarin中构建并生成.dll文件
  3. 现在在目标应用程序项目中,添加对上述.dll文件的引用,或者在解决方案中包含绑定项目并向其添加项目引用。
  4. 将com.optimizely URL方案添加到plist文件(根据xcode项目)
  5. AppDelegate.FinishedLaunching中添加与此类似的代码:
  6.  
    

    public override bool FinishedLaunching(UIApplication app, NSDictionary options) { // create a new window instance based on the screen size window = new UIWindow(UIScreen.MainScreen.Bounds);

    ABTesting.Preregister();
    Optimizely.Optimizely.SharedInstance.VerboseLogging = true;
    Optimizely.Optimizely.StartWithAPIToken("***YOURTOKEN***", options);
    

    }

    1. 添加导出的属性&#34; Window&#34; :(不是100%确定是否需要)

      ABTesting.Preregister();
      Optimizely.Optimizely.SharedInstance.VerboseLogging = true;
      Optimizely.Optimizely.StartWithAPIToken("***YOURTOKEN***", options);
      

    2. [Export("window")] UIWindow window { get; set; }

      中,这个:

      AppDelegate.OpenUrl

    3. 对于ABTesting,C#不支持Objective-C Optimizely标头使用的C风格的宏,所以我设置了一个静态类来封装我们所有的A / B变量。目前我们只有一个整数变量&#34; onboardingExperience&#34;。

    4. 
      public override bool OpenUrl(UIApplication application, NSUrl url, string sourceApplication, NSObject annotation)
      {
          if (Optimizely.Optimizely.HandleOpenUrl(url))
              return true;
      }
      

      1. 然后在其他地方我们只是引用 public static class ABTesting { public static void Preregister() { Optimizely.Optimizely.Preregister(_onboardingExperienceKey); }

            public static int OnboardingExperience
            {
                get
                {
                    return Optimizely.Optimizely.NumberForKey(_onboardingExperienceKey).IntValue;
                }
            }
        
            static OptimizelyVariableKey _onboardingExperienceKey = 
                OptimizelyVariableKey.Create("onboardingExperience", NSNumber.FromInt32(0));
        
        }
        

      2. 注意:

        由于Xamarin库执行的线程检查被Optimizely SDK违反,因此绘制Optimizly in-app手势可能会使调试模式版本中的应用程序崩溃。 (这可能只发生在子类UIView类中 - 例如:对我们来说,它在UIButton的子类中崩溃了。)

        并非所有Optimizely SDK都受到约束。有些功能和API需要在ApiDefinition.cs中写入适当的签名来支持这些功能。

        简化变量实现会很好,所以它不是那么冗长/重复 - 也许用C#反射和属性驱动它。

        祝你好运!