• Popular
  • Users
  • Login
Flic Home

Community

  • Login
  • Search
  • Popular
  • Users

iOS Swift Question: No callback happens when grabbing button

Developers
2
3
1.6k
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • niklas.landin
    niklas.landin last edited by 4 May 2018, 13:50

    I got the ios-boiler-plate application to work, but now it doesn't anymore.

    I use:
    @IBAction func grabButton() {
    print("Grabbing a flic..")
    SCLFlicManager.shared()?.grabFlicFromFlicApp(withCallbackUrlScheme: "wios-boilerplate-swift")
    }

    to call the flic app, which opens up correctly.
    But after selecting the button the flic app doesn't correctly call back to the boiler plate app anymore.
    Thus
    func flicManager(_ manager: SCLFlicManager, didGrab button: SCLFlicButton?, withError error: Error?) {
    print("I grabbed the button")
    if (error != nil) {
    print("Error: (error!._domain) - (error!._code)")
    return
    }
    // TODO: Here would be a good place to set the Flic latency in case you need lower latency
    // Consider choosing your prefered triggerBehavior as well (Click / hold is default)
    }

    is not called anymore.

    I have no clue of how to track down this error. But I suppose I'm not the first one experiencing this error.

    If anyone has a clue I would greatly appreciate it.

    Thanks,

    //Niklas

    1 Reply Last reply Reply Quote 0
    • niklas.landin
      niklas.landin last edited by 8 May 2018, 19:17

      Yes, that fixed the problem.

      Thank you!

      //Niklas

      1 Reply Last reply Reply Quote 0
      • oskar
        oskar FlicTeam last edited by 8 May 2018, 09:07

        Hi!

        It seems the boilerplate project references an old version of the fliclib.

        You can update by navigating to the fliclib-ios and running "git pull" and "git checkout master".

        I will update the boilerplate to use the latest version by default, thank you for bringing this to our attention!

        1 Reply Last reply Reply Quote 0
        2 out of 3
        • First post
          2/3
          Last post