I'm also having the same issue. Removing the assertion obviously removes the AssertionError, but I'd like to know more about why the assertion was added in the first place.
According to PHP docs, "assertions should be used as a debugging feature only."
Should a condition be added to return NULL if $result is not numeric or is empty? Or is it safe to remove the assertion completely? It doesn't seem to cause any issues in my testing, so this patch can be RTBC if a maintainer doesn't have any concerns.
Resolved by https://www.drupal.org/project/simple_feedback/issues/3419801 📌 Drupal 10 compatibility Fixed
Tested and works great in Drupal 10.2.3
scott.allison → made their first commit to this issue’s fork.
Attaching patch.
scott.allison → created an issue.