motion-testflight 1.4 → 1.5

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: bf654050bf3b2c9c27164dc95d7bf3d74a57b399
+  data.tar.gz: d1ed9f84b5f93c05a732be4bc8e16b67d312034b
+SHA512:
+  metadata.gz: f87d56de278d7477681ac23ebdb1c5bf7b44caf4e5df472cdb0ad2eaf84f36152f660af9290b7c56edbe335004952b315f46e078c75e0ed190565a7f98b6338d
+  data.tar.gz: 162e441dacde0a0bf16f21a3b48c0f24e3cbb4686e005185080adc24999c4bb07297561381f868abde0179b495de7f89f5f92ea342f5d9ca909de3d1a590a57c

data/README.rdoc

@@ -36,12 +36,22 @@ SDK and be submitted to the TestFlight platform.
            app.testflight.api_token = '<insert your API token here>'
            app.testflight.team_token = '<insert your team token here>'
            app.testflight.notify = true # default is false
+           app.testflight.identify_testers = true # default is false
          end
        end
      end
 
    You can retrieve the values for +api_token+ and +team_token+ in your TestFlight account page.
 
+   If you're using Testflight 1.2 or above, you should also add the app_token.
+  
+      # ...
+      app.testflight do
+        # ...
+
+        app.testflight.app_token = '<insert your APP token here>'
+      end
+
 4. (Optional) You can also set up distribution lists, if needed.
 
      Motion::Project::App.setup do |app|

data/lib/motion/project/testflight.rb

@@ -27,7 +27,7 @@ unless defined?(Motion::Project::Config)
 end
 
 class TestFlightConfig
-  attr_accessor :sdk, :api_token, :team_token, :distribution_lists, :notify
+  attr_accessor :sdk, :api_token, :team_token, :app_token, :distribution_lists, :notify, :identify_testers
 
   def initialize(config)
     @config = config
@@ -48,8 +48,18 @@ class TestFlightConfig
     create_launcher
   end
 
+  def app_token=(app_token)
+    @app_token = app_token
+    create_launcher if team_token
+  end
+
+  def identify_testers=(identify_testers)
+    @identify_testers = identify_testers
+    create_launcher
+  end
+
   def inspect
-    {:sdk => sdk, :api_token => api_token, :team_token => team_token, :distribution_lists => distribution_lists}.inspect
+    {:sdk => sdk, :api_token => api_token, :team_token => team_token, :app_token => app_token, :distribution_lists => distribution_lists}.inspect
   end
 
   private
@@ -61,7 +71,8 @@ class TestFlightConfig
 
 if Object.const_defined?('TestFlight') and !UIDevice.currentDevice.model.include?('Simulator')
   NSNotificationCenter.defaultCenter.addObserverForName(UIApplicationDidBecomeActiveNotification, object:nil, queue:nil, usingBlock:lambda do |notification|
-  TestFlight.takeOff('#{team_token}')
+  #{'TestFlight.setDeviceIdentifier(UIDevice.currentDevice.uniqueIdentifier)' if identify_testers}
+  TestFlight.takeOff('#{app_token || team_token}')
   end)
 end
 EOF

metadata

@@ -1,15 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: motion-testflight
 version: !ruby/object:Gem::Version
-  version: '1.4'
-  prerelease: 
+  version: '1.5'
 platform: ruby
 authors:
 - Laurent Sansonetti
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2012-10-26 00:00:00.000000000 Z
+date: 2013-04-01 00:00:00.000000000 Z
 dependencies: []
 description: motion-testflight allows RubyMotion projects to easily embed the TestFlight
   SDK and be submitted to the TestFlight platform.
@@ -24,26 +23,25 @@ files:
 - lib/motion-testflight.rb
 homepage: http://www.rubymotion.com
 licenses: []
+metadata: {}
 post_install_message: 
 rdoc_options: []
 require_paths:
 - lib
 required_ruby_version: !ruby/object:Gem::Requirement
-  none: false
   requirements:
-  - - ! '>='
+  - - '>='
     - !ruby/object:Gem::Version
       version: '0'
 required_rubygems_version: !ruby/object:Gem::Requirement
-  none: false
   requirements:
-  - - ! '>='
+  - - '>='
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 1.8.23
+rubygems_version: 2.0.3
 signing_key: 
-specification_version: 3
+specification_version: 4
 summary: TestFlight integration for RubyMotion projects
 test_files: []