Thanks for pointing this out!

For the moment you can work around this in a few ways:

1. In this specific case, documentSnapshot.getData() will return a Map<String, Object> containing the values you want ("wow" and 32). Of course you're likely interested in getting a Map of more interesting complex types and this doesn't handle that.

2. If you know the keys ahead of time, you can create a simple wrapper struct

class DudeWhateverHolder {
  public String dude;
  public int whatever;
}

snapshot.toObject(DudeWhateverHolder.class);

3. Alternatively, get(String, Class<T>) methods on the snapshot will also pull out complex values:

String dude = snapshot.get("dude", String.class);
int whatever = snapshot.get("whatever", Integer.class);

4. If you have some specific homogeneous type you're trying to load then you can declare a subclass of the map you want like so:

class DudeWhateverMap extends HashMap<String, MyClass> {}

// Usage
snapshot.toObject(DudeWhateverMap.class);

5. If you have lots of these you can also emulate the missing toObject(new GenericTypeIndicator<Map<String, MyClass>>() {}) with something like this:

public static <T> Map<String, T> toMapWithValues(Class<T> valueClass, DocumentSnapshot snapshot) {
  Map<String, T> result = new HashMap<>();
  for (String key : snapshot.getData().keys()) {
    T value = snapshot.get(key, valueClass);
    result.put(key, value);
  }
  return result;
}

// Usage
toMapWithValues(MyClass.class, snapshot);

Of course built-in support would be better, but the error message is erroneously pointing to a feature that doesn't exist rather than just a missing class. Fixing this isn't trivial and will require an additional public API review process so it won't happen too quickly.

Note that for heterogeneous values like those in your example (String and Integer), GenericTypeIndicator won't really help. The common supertype of values in your example would be Object and passing toObject(new GenericTypeIndicator<Map<String, Object>>() {}) would be essentially equivalent to calling getData().

Oh, and to be clear, I've added this to our backlog, but given the available workarounds we'll prioritize this along with other feature work.

Still needed!

Nothing yet?

We are still busy with a lot of other work, so unfortunately you have to apply the existing workarounds.

If no time to implement it, at least, workarounds should be in the documentation.

No news here?

Hi @Skaldebane ,

The team is discussing this feature request (b/123794691). In the meantime we will update the error message.