pup | Pluggable Micro Packager

File? means that this object can be either File or null, while the File type can't be null and it will throw an error if you try to make it null. To solve your problem you can either change type of the parameter of your function (the function where you pass data from this Future) from File to File? or if you can guarantee that .getFile() won't ever return null, you can put an bang operator (!) after your function call like this:

I think it would be a good idea to have the data about what to select in an array/object.

I guess there are a lot of new stuff here, but notice especially that the data item is inserted into the option element as itemdata. This is a trick for passing around data.

The specificity for the selector .wrapper-active that is applying the transform to show the navigation has a lower specificity value than menu .wrapper, which is also defining a transform. This is causing the transform: translateX(-100%); to take over.

Adding more specificity to the active class should do the trick:

There are a couple of issues I see on your code.

In your showbtn() function, your using the getElementsById function, but as far as I am aware, this doesn't exist. Were you trying to execute getElementsByName instead?

Either way, that would return a NodeList that you'd have to iterate over, and I see that you're trying to check the onchange, which in itself is an assignable property. That wouldn't work as expected.

I feel like you could simplify your logic by checking if at least one of your tags has a selected value that isn't "". Below is a simple suggestion - you can simplify if you want to by creating easier-to-select elements (either by names or class names, which would work with getElementsBy) // Array of select IDs. var arrayOfSelects = ['DHOps', 'LUOps', 'LTLOps', 'FEDEXOps']; // Iterate on each one. for (let select of arrayOfSelects) { var e = document.getElementById(select); // Checking if there is a selected value that isn't null, undefined, 0 or empty. if (e.value) { document.getElementById("submit").style.display = "block"; break; } }

I can't reply to the above issue (need more reputation) but can confirm that I am seeing the same behaviour. What makes it even more weird is that the issue only presents itself when the user attempts to perform the OAuth integration with an account that is already signed in. The user is presented with a generic “Sorry, something went wrong there. Try again.” error before even seeing the required scopes list. However if the user is not logged into their account, and logs in as part of the OAuth integration, then there is no error and integration can be completed successfully. The fact that this issue doesn't affect users who aren't logged in shows that the setup (callback API, credentials.json, etc.) is all correct. I believe this issue has been introduced in the last month or so.

The Flow pups is producing updated values as you can see in my logcat

Not exactly.

The Flow is emitting the same List of the same Puppy objects. I believe that Compose sees that the List is the same List object as before and assumes that there are no changes.

My suggested changes:

• Make Puppy be an immutable data class (i.e., no var properties)

• Get rid of changeFlow and have getPuppies() return a stable MutableStateFlow> (or make that just be a public property)

• In toggleAdoption(), create a fresh list of Puppy objects and use that to update the MutableStateFlow>:

i did this to get the class name :

It is likely due to your network problem. Because the output says (server unavailable).

Ways to debug this:

1. Try curl https://google.com to see whether your command line can connect to network.
2. Also try, for example, curl https://flutter.dev (or, try to curl the actual url your pub get is trying to access.

This may due to, for example, your network is broken. Or because you have a broken VPN, broken proxy, etc.