Skip to content
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.

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

Update fyber marketplace 7.4.1 #200

Closed

Conversation

AsafKoskiWork
Copy link
Collaborator

  • updated used FMP version to 7.4.1
  • Add a null check for completion callback. Potential crash fix
  • Convert app ids collection to set, so the warning message will only appear if we have multiple unique app ids

@@ -178,21 +178,23 @@ public void initialize(Context context,
private void waitForInitializationStatusAndReport(
final @NonNull InitializationCompleteCallback completionCallback) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nonnull is already checking whether it is null or not. I don't think a null check is necessary here.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Apparently it is necessary, please see #213

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is another proposed fix for this in pull request #209

if (configuredAppIds.size() > 1) {
String message = String.format("Multiple '%s' entries found: %s. " +
"Using '%s' to initialize the Fyber Marketplace SDK.",
KEY_APP_ID, appIdForInitialization, appIdForInitialization);
KEY_APP_ID, configuredAppIds, appIdForInitialization);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ConfiguredAppIds returns instances of set object some thing like this '@61bbe9ba'. So, I think it should be appIdForInitialization.

@joshuajplagonera
Copy link
Collaborator

Obsolete PR. Closing...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants