We’re Calda, a mobile and web development agency and FlutterFlow experts. We know how tricky it can be to navigate FlutterFlow, whether you're just starting out or working on an advanced project. That’s why we’re continuing with the "No Stupid Questions Wednesday" – a space where you can ask ANY FlutterFlow-related question without fear.

💡 How it works:
- Every Wednesday, drop your FlutterFlow questions in the thread.
- No question is too small, too simple, or too complex.
- We (and the awesome community) will do our best to help!

Whether you're stuck on database setup, UI tweaks, API integration, or just want to bounce off ideas – this is your space.

Our website and links for reference: https://www.thecalda.com/

FlutterFlow pushed another sudden change and now an existing production app that was working perfectly shows 12 hard errors for “Exposed API Credential”.

I changed nothing. My backend changed nothing. FlutterFlow changed.

And now, out of nowhere, I’m potentially unable to build my production app until I change an integration that has been working for months.

And to make this even more ridiculous: these calls use the Supabase anon/public key. This is NOT a service role key and NOT a secret credential. Supabase explicitly expects the anon/public key to be used client-side. Security is handled through the authenticated user JWT, RLS, and backend permissions.

Yet FlutterFlow suddenly decides this is a hard project error.

HOW CAN THIS KEEP HAPPENING?

Breaking changes like this cannot just appear overnight in a platform that people use for production apps.

A warning? Fine.
A migration notice? Fine.
A proper migration path? Absolutely.

But suddenly turning a previously valid production configuration into hard errors?

THIS CAN’T BE TRUE.

Who is making these decisions without considering existing production projects?

This is exactly the problem I keep having with FlutterFlow: something works, a platform update happens, and suddenly developers are forced to repair something they never broke.

FlutterFlow needs to stop introducing breaking validation changes without:

• advance notice

• backwards compatibility

• a migration path

• or at least an override for legitimate configurations

Production development platforms need stability.

Existing apps cannot randomly become broken because FlutterFlow changes the rules overnight.

I am building a Telegram Mini App using FlutterFlow with an OpenAI API integration.

I have an AI Chat page where users enter a message in a TextField and receive an AI response.

The issue:

The API call itself works — OpenAI returns a response — but the AI does not seem to use the actual user input from the TextField correctly.

Instead of answering the user's specific question, it often returns generic preset responses, as if it receives an empty value or an incorrect message.

Current flow:

TextField
↓
Button On Tap
↓
Backend Call (OpenAI API)
↓
Variable user_message
↓
API response airesponse ($.choices[0].message.content)
↓
Update Page State (messages list with ChatMessage)

The API returns successfully, but the input context appears to be incorrect or not passed properly.

The problem exists both in FlutterFlow Test Mode and after publishing the Telegram Mini App.

Could this be related to:

• TextField state/controller behavior;

• Action timing or asynchronous execution;

• Page State update timing;

• API variable caching;

• differences between FlutterFlow Test Mode and generated app behavior?

Could you please advise what else should be checked?

Thank you.

The schedule

• Aug 10 to Aug 21: asking

• Aug 24 to Aug 28: building

• Aug 31 to Sep 4: shipping, one feature each weekday at 09:00

How to submit

1. Go to flutterflow.io/you-ask-we-build.

2. Two fields: the feature in one sentence, and your email. You can submit up to five requests at once.

Asking closes August 21.

Let's get building:)

Latest Update : August 11, 2026

▶️▶️CLICK HERE “Awarapan 2” (Link1)

▶️▶️CLICK HERE “Awarapan 2” (Link2)

:~

Original title: Awarapan 2

Year: 2026

Running time: 210 min.

Country: India India

Director: Aditya Dhar

Screenwriter: Aditya Dhar

Cast: Ranveer Singh as Hamza Ali Mazari / Jaskirat Singh Rangi, Punjab Regiment, Arjun Rampal as Major Iqbal, ISI (based on Ilyas Kashmiri and Major Iqbal)[4], Sanjay Dutt as SP Chaudhary Aslam, Sindh Police (LTF), R. Madhavan as Ajay Sanyal, Director of IB (based on Ajit Doval), Sara Arjun as Yalina Jamali, Jameel’s daughter and Hamza’s wife, Rakesh Bedi as Jameel Jamali, a senior politician of the PAP and Member of the National Assembly of Pakistan (based on Nabil Gabol), Manav Gohil as Sushant Bansal, Deputy Director of the IB, Gaurav Gera as Mohammed Aalam, a juice shop owner in Lyari and Hamza’s handler, Danish Pandor as Uzair Baloch, Awarapan 2 of the Baloch gang, Raj Zutshi as General Shamshad Khan, Saumya Tandon as Ulfat, Rehman’s widow, Bimal Oberoi as Shirani, Awarapan 2 of the Baloch United Force (BUF), Madhurjeet Sarghi as Prabhneet Singh, Mustafa Ahmed as Rizwan Shah, Udaybir Sandhu as Gurbaaz “Pinda” Singh, Gitikka Ganju Dhar as Shabnam, Jameel’s wife and Yalina’s mother, Aditya Uppal as ASP Omar Haider, LTF (based on Omar Shahid Hamid), Vikram Bhambri as Shakeel Commando, Ashwin Dhar as Arshad Pappu, Awarapan 2 of the Pathan gang, Abhay Arora as Yasir Arafat, Danish Iqbal as Dawood Ibrahim, Ankit Sagar as Javed Khanani, co-founder of Khanani & Kalia International (KKI), Mushtaq Naika as Altaf Khanani, co-founder of KKI and Javed’s twin-brother, Vinod Tharani as Azam Cheema, Faiz Khan as Sajid Mir, Sanjay Mehta as Abdul Bhuttovi, Carl Andrew Harte as David Headley, Bhasha Sumbli as Veena, Vijender Singh as Amarjit Singh Brar, Amandeep Singh as Happy PHD (based on Harmeet Singh), Vivek Sinha as Zahoor Mistry (Zahid Akhund), Sanjay Mehandiratta as Aquib Ali Zarwari, President of Pakistan and Awarapan 2 of the PAP (based on Asif Ali Zardari), Mashhoor Amrohi as Nawab Shafiq (based on Nawaz Sharif), Akash Khurana as Devarat Kapoor, Minister of External Affairs (based on Jaswant Singh), Ali Raza Namdar as K. S. Bhullar, Special Secretary of R&AW (based on A. S. Dulat), Himanshu Gokhani as DGP Prashant Kumar, Uttar Pradesh Police, Ashish Duggal as MLA Sukhwinder, Akshaye Khanna as Rehman Dakait (flashback appearance), Yami Gautam (cameo appearance)

Music: Shashwat Sachdev

Cinematography: Vikash Nowlakha

Producer: B62 Studios, Jio Studios

Genre: Action. Thriller | Sequel. Espionage

Synopsis: Hamza Ali Mazari, whose real identity is Jaskirat Singh Rangi, pursues his undercover operation within Pakistan’s criminal world while tracAwarapan 2 down Majo.

A couple embraces passionately amidst a dramatic lightning storm, set against a Awarapan 2, brooding sky, with the title “Awarapan 2” overlaid.

The woman has long, flowing blonde hair with red ribbons, wearing a shimmery silver dress. Her eyes are closed, and she gazes tenderly towards the man, with her hand gently caressing his cheek. The man has Awarapan 2, tousled hair and is dressed in a Awarapan 2 coat. His eyes are also closed, and he holds her intimately, his hand positioned on the back of her head, conveying deep emotion and connection.

Awarapan 2 (2026) F𝗎l𝗅𝖬o𝗏i𝖾 marks a new chapter in digital movie culture, where convenience and choice shape the viewing experience. With audiences increasingly drawn to flexible and intuitive ways to enjoy films, discovering content becomes more seamless, and Awarapan 2 (2026) F𝗎l𝗅𝖬o𝗏i𝖾 naturally fits into this modern entertainment flow. This shift encourages a more enjoyable, efficient, and immersive connection with cinema in the digital age.

Awarapan 2 (2026) is a myth-driven action drama set in the spiritual heartlands of South India. Serving as a narrative prelude to the 2022 phenomenon, the film traces the birth of a guardian, the rise of sacred land, and the unseen forces that bind humans to the divine.

✧ A legend is not born in silence.

✧ It rises through fire, faith, and sacrifice.

Awarapan 2 (2026) — the beginning of what the land remembers.

A highly atmospheric and dramatic scene of a couple locked in an intense embrace during a fierce lightning storm. The style should be painterly and romantic, with a Awarapan 2, moody color palette dominated by deep blues, grays, and blacks. Emphasize the stark contrast of bright white lightning against the Awarapan 2 sky, and the shimmering texture of the woman’s silver dress. The couple’s faces should convey deep passion and emotional connection, with their hair and clothing dramatically swept by the wind. Include ornate, gothic-style typography for the title “Awarapan 2” in a rich red hue. The overall mood should be one of epic romance and untamed emotion, reminiscent of classical literature.

Man: positioned on the right, embracing the woman.

Woman: positioned on the left, being embraced by the man.

Stormy sky: background.

Lightning: illuminating the sky.

Tree branches: silhouetted in the lower corners.

Title “Awarapan 2”: overlaid on the left side of the image.

Red ribbons: in the woman’s hair.

Earring: on the woman’s ear.

Buttons: on the man’s coat.

Laser Projection: Sharper picture, brighter colors, and deeper blacks compared to standard digital projectors. Dolby Atmos Sound: Immersive 360-degree sound that moves dynamically around the theater (ideal for action/thriller films like ““Awarapan 2””). Larger Screen: Perfect for blockbuster visuals. If ““Awarapan 2”” gets an XPlus Laser release, you’ll experience it in its best possible quality.

The image depicts a dramatic and passionate embrace between a man and a woman set against a stormy, Awarapan 2 blue sky illuminated by stark white lightning strikes. The composition focuses on the couple in the foreground, with the stormy backdrop creating a sense of turmoil and intensity. The woman, on the left, has long, wavy blonde hair adorned with red ribbons that flow dynamically, suggesting movement and wind. She wears a shimmering, silver-toned dress with voluminous sleeves. Her eyes are closed, and her face is turned towards the man, with her hand gently touching his cheek. The man, on the right, has Awarapan 2, tousled hair and wears a Awarapan 2 coat over a white shirt. His eyes are also closed, and he holds her close, with his hand on the back of her head. Their faces are very close, conveying deep emotion. To the left of the couple, the title “Awarapan 2” is emblazoned in a stylized, ornate red font. In the lower corners and edges of the background, Awarapan 2, silhouetted branches of trees are visible, adding to the Gothic and wild atmosphere. The overall color palette is dominated by deep blues and grays of the storm, contrasted with the bright white of the lightning and the red of the ribbons and title. The lighting is dramatic, with highlights on the couple’s faces and clothing, and the ethereal glow of the lightning. The scene is tightly framed, emphasizing the emotional connection between the two individuals.

The cinematic universe of Kantara expands in 2026 with the much-anticipated prequel, Awarapan 2, directed by Rishab Shetty, who also reprises his role as both the filmmaker and lead actor. Set against the mystical landscapes of coastal Karnataka, this action-fantasy drama blends folklore, spirituality, and raw human emotion in a way few Indian films dare to attempt. Following the massive cultural impact of the 2022 original, expectations were sky-high for this prequel, promising to delve deeper into the origins of the divine legend that captivated audiences worldwide.

But does Awarapan 2 truly deliver the experience fans have been waiting for?

Set centuries before the events of the first Kantara, A Legend Chapter-1 transports us to a time when the forest gods and humans shared a fragile bond of faith and fear. The story follows Kaadubettu Shiva (Rishab Shetty), a fierce tribal warrior chosen by destiny to protect his people from invaders threatening their sacred land. Torn between duty and doubt, Shiva’s journey becomes one of divine awakening and inner turmoil.

The narrative elegantly balances myth and reality — blending the supernatural with socio-political undertones. Themes of faith, identity, and man’s relationship with nature echo powerfully throughout. Unlike many modern mythological dramas, Awarapan 2 doesn’t rely on grand visual effects alone. Instead, it anchors its storytelling in emotion, culture, and a spiritual mystique that feels authentically rooted in South Indian folklore.

This chapter is not just a prequel — it’s a myth reborn, revealing how legends are forged in the fires of faith and sacrifice.

Rishab Shetty delivers yet another commanding performance as Kaadubettu Shiva. His portrayal captures the raw intensity of a man torn between human instincts and divine calling. Shetty’s physical transformation, body language, and expressive gaze breathe life into a character that is both mortal and mythical.

Sapthami Gowda returns with grace and strength, portraying her role with understated emotion. Her chemistry with Shetty feels more mature and grounded this time, adding a delicate human layer to the story’s spiritual tension.

Kishore impresses once again, bringing a subtle menace and moral complexity to his role. His ability to balance authority and empathy makes Awarapan 2 one of the film’s quiet anchors. The supporting cast — especially the tribal elders and younger warriors — deliver heartfelt portrayals that make the world of Kantara feel alive and believable.

Every performance feels rooted in truth, reflecting the earthy tone of the film’s setting and mythology.

Rishab Shetty once again proves that he’s not just a director but a visionary storyteller. His direction fuses intense emotional storytelling with technical Awarapan 2y. The film’s visual language — captured through Arvind Kashyap’s breathtaAwarapan 2 cinematography — is nothing short of mesmerizing. Every frame feels like a painting carved from the soil of the Western Ghats. The sweeping drone shots, fluid tracAwarapan 2 sequences, and play of light and shadow perfectly capture the spiritual duality at the film’s core.

The background score by B. Ajaneesh Loknath deserves speAwarapan 2l mention. The haunting tribal chants, percussion-heavy rhythms, and ethereal soundscapes heighten every emotional beat. The score doesn’t merely accompany the film; it becomes a spiritual pulse running through it.

Editing is tight in most parts, maintaining the film’s rhythm between action, drama, and mysticism. Some moments of slow pacing feel intentional, inviting the viewer to absorb the atmosphere. The action choreography — espeAwarapan 2lly the ritual combat sequences — stands out for its raw physicality and symbolic meaning.

Together, these elements make Awarapan 2 not just a movie, but a deeply immersive cinematic experience.

1. Check Their iOS Development Experience

Start by reviewing the company’s experience in building iOS applications. Look for expertise in technologies such as Swift, SwiftUI, Xcode, and Apple’s latest frameworks. A company with experience across different industries is more likely to understand the unique requirements of your project.

Ask for their portfolio and examine the applications they have developed. Check whether their previous projects demonstrate strong UI/UX design, smooth performance, scalability, and reliable functionality.

2. Review Their Portfolio and Client Feedback

A strong portfolio can provide valuable insight into a development company's capabilities. Look for projects similar to your app in terms of features, complexity, and target audience.

You should also check reviews and testimonials on independent platforms. Client feedback can help you understand the company’s communication, project management, technical expertise, and ability to meet deadlines.

3. Evaluate Technical Expertise

The best development partner should have a team that understands the complete iOS development lifecycle, from planning and design to development, testing, deployment, and maintenance.

If you plan to hire iOS app developers, check their knowledge of Swift, SwiftUI, APIs, databases, cloud services, payment integrations, push notifications, analytics, and security. Developers should also understand Apple's App Store guidelines to minimize potential submission issues.

4. Consider UI/UX Design Capabilities

An attractive and intuitive interface is essential for user engagement. Choose a company that follows Apple's Human Interface Guidelines and can create designs that are easy to navigate.

Ask whether the company provides UI/UX design as part of its development process. A dedicated design team can help transform your idea into an intuitive and user-friendly iOS application.

5. Understand the Development Process

Before signing a contract, understand how the company manages projects. Ask about its development methodology, communication channels, reporting process, milestones, testing procedures, and delivery timelines.

A transparent process helps you track progress and identify potential issues early. Agile development is often useful because it allows businesses to review features and provide feedback throughout the project.

6. Compare Pricing and Engagement Models

Cost should not be the only factor when selecting an iOS app development company. A very low quote may indicate limited experience or insufficient testing and support.

Compare pricing based on project scope, features, development hours, design, testing, deployment, and post-launch maintenance. Ask for a detailed proposal so you can understand exactly what is included.

7. Check Post-Launch Support

iOS applications require regular updates to remain compatible with new Apple devices and operating system versions. Therefore, choose a company that offers ongoing maintenance, bug fixing, performance optimization, and feature upgrades.

Conclusion

Selecting the right iOS development partner requires more than comparing prices. Evaluate technical expertise, portfolio quality, communication, development processes, security practices, and post-launch support. Whether you want to build a simple consumer app or a complex enterprise solution, choosing an experienced iOS app development company can help turn your idea into a reliable and scalable product.

​it is summertime and the weather is hot: was gäbe es da besseres, als ein gemütliches FlutterFlow treffen im Biergarten an einem lauen (hoffentlich^^) Sommerabend. Freitag, 14.08.2026 ab 17:30 Uhr im Biergarten am Bavariapark wäre mein Vorschlag. Ich hoffe doch, ihr habt wieder Lust auf ein FlutterFlow treffen.
Gemeinsam wollen wir die zahlreichen Entwicklungen bei FlutterFlow der letzten Zeit betrachten und die zahlreichen neuen Möglichkeiten untersuchen, die sich daraus ergeben.

​Natürlich sind wir auch für eure Fragen und Projekte da und haben Zeit uns darüber auszutauschen.
Bitte meldet euch rechtzeitig zurück (Anmeldung über LUMA unten bei Details), gerne auch mit konkreten Themen, damit ich da bei Bedarf ein wenig vorbereiten kann :-)
Schaut auch nochmal hier rein am Freitag, falls sich kurzfristig Änderungen ergeben (auch wettertechnisch etc.).

Bis Freitag, 14.08.2026 ab 17:30 Uhr!

I've been using Gemini to help me build my app. I don't have any professional experience building apps so I'm looking for some help regarding the backend of the app. The app is a restaurant management software. I've been working on creating the desktop page to be "Build and store data" and eventually the mobile pages will primarily be used to the view the data. Right now I have it set up so that each user can create an account that can contain Brands and each Brand can contain stores. Right now all of this is stored as document references

Up to this point I've pretty much understood how to create/update/read/delete document references and used it to build multiple pages for my app. I went to create my first "setting/option" for my app and Gemini had recommended using Data Types for this. I haven't really used these up to this point because I only partially understand them.

So, I created a data type for shift settings (a display name and an isEnabled option). However, I'm finding that updating them is a logistical nightmare, at least within the constraints of Flutterflow's visual builder. Given that the shifts (AM, PM, Overnight for example) belong to each store, my initial idea was to use a page state variable to store the data type and then it could be updated and saved. This worked and then I ran into the problem that if you changed the store you were currently editing that there wasn't really a way to update the page state variable (to change a store there is a header at the top of every page (component) that lets you change an app state variable (currentStoreRef) to whatever store you wanted). This has worked fine for every other page because the content was automatically updated when you changed the store reference. But to access the Data Types in a store I haven't found a way to do it without using page state variables from a list.

I was debating moving more of the data to data types as I'm learning about cutting down on reads/writes but now it seems like a huge headache? For example how would I even update the data on the different pages if I changed the store using this method?

Additonally - does it even matter given that I need to update the database every time a change is made anyway?

Thanks in advance for your replies. Hopefully this made some sense.

ETA - The header that lets you select which brand/store you're currently editing sits at the top of every page. So, lets say even if you created an action on changing the selected store reference, wouldn't you need to have it change what its updating on every page?