I wanted to let you know that even though there aren’t any new updates just yet, the issue is actively being addressed. As mentioned earlier, the external mobile app team is investigating this, and we’re waiting for their findings. We’ll be sure to keep you updated as soon as we hear back from them.
We truly apologize for the ongoing frustration this might be causing and we appreciate your continued patience and understanding.
Thank you for your patience and understanding as we work towards a solution.
Same Issue here. How is possible make.com didn’t fix this issue after a month? This is a urgent fix as notification android module is the only way notify people with our scenarios. Please escalate as priority issue.
Our external mobile app team is investigating the issue in order to develop a solution. Unfortunately, we don’t have any new updates at this stage but we will keep you updated as soon as we have any new information.
We sincerely apologize for the continued disruption and we appreciate your patience and understanding.
@Michaela instead of making your users suffer for months, how about you can enable the TEXT MESSAGE feature of Make app (which usually costs money).
So instead of using BROKEN push notification we can actually reconfigure our scenarios to be notified by TEXT. Just de-monetize that feature until your “external mobile app team” does their job. Which I’m going to go ahead and say again, is ridiculous that this critical issue is unfixed after this long.
Unfortunately, we don’t have any new updates to share at the moment. However, the team continues to work on finding a solution. We’ll keep you informed as soon as there’s progress.
We sincerely apologize for the ongoing disruption and we truly appreciate your patience and understanding.
There needs to be some sort of official work around that is published and some compensation to users that have had scenarios impacted by this massive disruption.
Push notifications were an integral part of our workflow for fulfillment, and it’s costing us money to be without it, and will cost us money to temporarily or permanently replace it. And we’re relatively small scale.
I figured we’d be looking at a few weeks at the worst, and we’re at 3 months now with zero sign of progress… You guys need a new “external” mobile dev.
The official Make support response is now recommending to use an additional, third party SMS service to fix this issue.
Sorry about that; unfortunately, this is a known issue while working with the Android and iOS apps. This has been reported to our dev team already.
Please use a dedicated SMS-sending service instead.
There is a further cost to using another service. Subscription, usage, setup time.
The website still lists push notifications as a feature.
Where is the compensation for impacted users due to a terminal failure of a core advertised feature? This has been costing us money for nearly 4 months now, and the official solution is now telling us to spend more money to fix Make’s problem…
We’re truly sorry for the disruptions this issue has been causing, and we completely understand that this is frustrating.
I see you’re already in touch with our team through the ticketing system, which is the best place to continue the conversation. They’ll be able to assist you directly and keep you updated on any new developments.
Thank you for your patience and understanding as we work through this.
Hi, @Michaela, is this going to be fixed within the next 2 weeks? (I beg you not to answer with “the team is looking into it”, just a “yes” or a “not likely”.)
I don´t mean it as an ultimatum but I do need to plan my move off the platform if not as I have lost money off of this problem (apart from still having to pay the Make sub.) I´m NOT looking for a refund, just a solution which doesn´t involve workarounds as this is obv. something that can be fixed and the lack of advance on the problem and lack of transparency with a repeated “we´re working on it” really paints a bad picture of Make.
Thank you for sharing your concerns and for your follow-up questions.
I’ve spoken with the development team, and while I cannot promise a resolution within the next two weeks, I can confirm that this issue is now being treated as a high priority. The team plans to dedicate focused effort to it starting next week or the week after.
I understand this likely isn’t the answer you were hoping for, and I’m truly sorry for the delay and the disruptions this has caused. Please know that we’re committed to addressing this thoroughly.
I’ll provide updates here as soon as there’s any news to share.
Make continues to do nothing about this issue. But constantly reassures users you’re working on it and a solution is coming soon. 4 months now the same old song and dance. Stop lying to your users and telling us the solution is in progress. That simply cannot be true. Push notifications is not a feature of Make! Stop the false advertising!
I still see you are charging money to send a Text message for the “Acid” feature. I thought I asked you to change that to be a FREE feature for the short term while “you’re working on it”. Make must really hate their users.
Well. I can only add some info, that the notification worked on Samsung Android 14, but are not working on Android 13 (worked there at least until the April of this year).
My name is Tereza, and I am the Product Manager responsible for the team developing and maintaining the built-in apps in Make.
I want to provide you with an update on the issue with the “Android > Push notifications” module that you have been experiencing.
Currently, our team is working on migrating the module to use the Firebase Cloud Messaging (FCM) API to restore its functionality.
I understand how frustrating it is not to be able to use the “Push notifications” module, and I sincerely appreciate your patience as we work on this migration.
With the Christmas holiday season approaching, we have implemented a freeze on releasing updates to the platform and apps. This precaution is necessary to minimize the risk of introducing breaking changes during a period when many of our colleagues are on vacation. As a result, we will not be able to release the fix until January.
We are planning to deploy the fix as soon as we can.
I appreciate your understanding and I wish you a peaceful holiday.
Hi Tereza,
I completely understand the freeze on updates during limited staffing periods, and I actually really appreciate the explanation for WHAT is actually being done to resolve the issue.
@Michaela told us on Dec 3rd it would be a focused effort no later than the 17th, and on the 20th you provided info that appears to indicate that has occurred and inferred a fix would be ready to deploy when updates are unfrozen in January.
However, we are now 3 weeks into January, and it is still broken with no additional updates from you.
At this point we’ve stuck with it for 5 months now, so any one who is going to move onto something else has done that, or found a workaround in our scenarios. Stringing us along with a carrot of “soon” isn’t helping anyone at this juncture, and doesn’t change anything.
Can you please give us some insight on a more accurate or more honest timeline for this deployment? If it’s genuinely unknown, then just say that.
