fix #1416 - ClassNotFound for FlowParameters

[dimipaun]

Fix for #1416
See https://stackoverflow.com/a/28589962/4548500 for details.

Hey there! So you want to contribute to FirebaseUI? Before you file this pull request, follow these steps:

• Read the contribution guidelines.
• Run ./gradlew check to ensure the Travis build passes.
• If this has been discussed in an issue, make sure to mention the issue number here. If not, go file an issue about this to make sure this is a desirable change.
• If this is a new feature please co-ordinate with someone on FirebaseUI-iOS to make sure that we can implement this on both platforms and maintain feature parity.

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

[dimipaun]

I signed it.

[googlebot]

CLAs look good, thanks!

[samtstern]

@dimipaun thanks for this! This will be in version 4.2.1 (or whatever version comes out next, might be 4.3.0)

[dimipaun]

It's all @SUPERCILEX , I just followed his lead!
I can't wait to give this a try, hopefully next release will be out soon.
As a side note, I can't believe we're the only people that have this issue.
How can this be? What am I missing?

[samtstern]

@dimipaun I have no idea why you're seeing this issue, or why others are not.

You can try this right now using the 4.2.1-SNAPSHOT builds if you just want to verify (see the main README for instructions).