9516ab1106
Most likely this would be because the user hasn't unlocked their device since last restart. This behavior existed once before, but the startup ordering is pretty delicate. So, we're now redundantly checking in SSK in case this delicate startup logic gets mis-ordered again. Also fixed the AppDelegate method to check for the proper applicationState, since it will never be "active" in didFinishLaunching. fixes https://github.com/WhisperSystems/Signal-iOS/issues/1627 // FREEBIE
19 lines
776 B
Ruby
19 lines
776 B
Ruby
platform :ios, '8.0'
|
|
source 'https://github.com/CocoaPods/Specs.git'
|
|
|
|
target 'Signal' do
|
|
pod 'SocketRocket', :git => 'https://github.com/facebook/SocketRocket.git'
|
|
pod 'AxolotlKit', git: 'https://github.com/WhisperSystems/SignalProtocolKit.git'
|
|
pod 'SignalServiceKit', git: 'https://github.com/WhisperSystems/SignalServiceKit.git', branch: 'mkirk/dont-reset-storage-before-first-unlock'
|
|
#pod 'SignalServiceKit', path: '../SignalServiceKit'
|
|
pod 'OpenSSL'
|
|
pod 'PastelogKit', '~> 1.3'
|
|
pod 'FFCircularProgressView', '~> 0.5'
|
|
pod 'SCWaveformView', '~> 1.0'
|
|
pod 'ZXingObjC'
|
|
pod 'JSQMessagesViewController'
|
|
target 'SignalTests' do
|
|
inherit! :search_paths
|
|
end
|
|
end
|