1. 07 Mar, 2012 1 commit
  2. 06 Mar, 2012 2 commits
  3. 22 Jan, 2012 1 commit
  4. 14 Jan, 2012 2 commits
  5. 13 Jan, 2012 2 commits
  6. 01 Dec, 2011 1 commit
    • In iOS 5, the ASIAuthenticationDialog could not be dismissed using either the Cancel button or automatically by successfully logging in.
      The bug is due to a change in UIViewController in iOS 5.  The class & instance "dismiss" methods are using [UIViewController parentViewController] which, as of iOS 5, no longer returns the presenting view controller.  A new property called 'presentingViewController' was added in iOS 5 to make up for this.
      
      Changed the class & instance dismiss methods to use the "presentingViewController" property if it is available (iOS 5+).  If not, it falls back to the "parentViewController" property.
      George Cox authored
  7. 04 Nov, 2011 1 commit
  8. 18 Oct, 2011 1 commit
    • Previously, tasks running from inside the CFRunLoop would call CFRunLoopStop prior to finishing execution. This results in non-deterministic failures to call endBackgroundTask when running iOS tasks in the background with beginBackgroundTaskWithExpirationHandler.
      Since the only reason to break out of the CFRunLoop is to flush the autorelease pool, we instead invoke CFRunLoopRunInMode with returnAfterSourceHandled=True, which safely returns and flushes the autorelease pool after each invocation of the CFRunLoop.
      Erik Chen authored
  9. 07 Oct, 2011 2 commits
  10. 06 Oct, 2011 1 commit
    • ASIFormDataRequest has a default 'GET' method (should be 'POST' by
      default)
      Frédéric VERGEZ authored
  11. 05 Oct, 2011 2 commits
  12. 19 Sep, 2011 5 commits
  13. 18 Sep, 2011 1 commit
  14. 17 Sep, 2011 5 commits
  15. 13 Sep, 2011 1 commit
  16. 11 Sep, 2011 2 commits
  17. 31 Aug, 2011 1 commit
  18. 24 Aug, 2011 1 commit
  19. 20 Aug, 2011 6 commits
  20. 18 Aug, 2011 1 commit
    • incorrectly charging the entire buffer size against the throttler
      rather than just the number of bytes actually read.
      
      For example, if you did a read with a 32KB buffer which only received
      300 bytes across the wire, the bandwidth Throttler would charge
      you for a full 32KB of bandwidth rather than the 300 bytes that
      were really used.  This was grossly overstating the bandwidth
      consumption to the throttler.
      Mike Belshe authored
  21. 10 Aug, 2011 1 commit