The above command will resize the Pool [default-pool] for your cluster to zero. The correct format is using the flag --size not --resize with the --zone flag as follows:
gcloud container clusters resize [cluster name] --size=0 --zone [cluster zone]
Good news, now you are able to do so through the console’s UI by editing the cluster, scrolling to Node pools, and changing the size to 0. (couldn’t verify for an IOS app). However, this may not solve your issue, as per this official note,
"Beginning with Kubernetes version 1.7, you can specify a minimum
size of zero for your node pool. This allows your node pool to scale
down completely if the instances within aren't required to run your
workloads. However, while a node pool can scale to a zero size, the
overall cluster size does not scale down to zero nodes (as at least
one node is always required to run system Pods)."
And per this Google groups discussion, “there needs to be at least some space for keeping the cluster operational”.
That said, an alternative in your case is to delete the node pool “in which it does not drain or reschedule”.
EDIT [2019.09.02] Noting there is no charge for the master node required to run system pods: See https://cloud.google.com/kubernetes-engine/pricing : "Because GKE abstracts away the existence of the master, you are not charged for the master node."