New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

NFC usage triggers SDK callback #7

Open

msmtamburro opened this issue Dec 29, 2022 · 0 comments

msmtamburro commented Dec 29, 2022 •

edited

Loading

When we use NFC in our app, we often see a blank bitlyResponse come through following an NFC operation. For example:

Bitly.initialize(
  bitlyAppId, 
  deviceId: deviceId, 
  supportedDomains: supportedDomains, 
  supportedSchemes: supportedSchemes
) { [weak self] (bitlyResponse, bitlyError) in
            /// WE UNEXPECTEDLY SEE RESPONSES WITH CERTAIN NFC OPERATIONS
}

In particular, the responses always look like this:

(lldb) po bitlyResponse?.makeStringDict()
▿ Optional<String>
  - some : "[\"statusText\": \"nil\", \"bitlink\": \"nil\", \"url\": \"\", \"applink\": \"nil\", \"statusCode\": \"nil\"]"

The text was updated successfully, but these errors were encountered:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment