ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Mobile & games · #appcelerator
Goal: Keep a low‑traffic Appcelerator Titanium app on the free ArrowDB (ACS) developer sandbox to avoid unexpected billing while still using SDK 8.0‑9.x. Constraints/uncertainty: The free sandbox provides up to 1 M API calls per month, but the switch to the paid plan occurs automatically and silently when the quota is exceeded, with no CLI or build‑log notif
Goal: receive background push payloads in an Appcelerator Titanium app on iOS 15+ without showing a system notification banner, while still waking the app to process the payload. Constraint: Ti.App.addEventListener('notification', ...) handles remote notifications, but the SDK does not expose a dedicated silent-push flag. Setting the APNs alert field to an e
Goal: Determine whether to enable certificate pinning with a backup pin and forced‑update mechanism or to rely on the platform trust store together with App Transport Security (ATS) exceptions for TLS validation in Ti.Network.HTTPClient. Constraint: Pinning protects against compromised CAs but causes hard failures when the server certificate rotates without
When managing long-running network requests in Appcelerator Titanium, there is a trade-off between using the timeout property and the abort() method to handle unresponsive servers or user-initiated cancellations. The timeout property ensures a request fails automatically after a set duration, typically triggering the onerror callback. In contrast, abort() al
The Appcelerator Titanium SDK utilizes session tokens via Ti.Cloud.Users.login to authenticate API requests. These tokens have a defined Time-to-Live (TTL), typically 24 hours, after which the server returns a 401 Unauthorized response for subsequent calls. While the SDK provides the mechanism to obtain these tokens, there is no built-in transparent renewal
The goal is to guarantee that a series of DDL statements applied through Ti.Database either fully succeed or leave the local SQLite database unchanged. Titanium supplies only low‑level SQLite access; there is no built‑in migration runner, and the explicit transaction API (BEGIN/COMMIT/ROLLBACK) varies across SDK releases, so developers often rely on a Ti.App
Native Toolchain Integration Appcelerator Titanium relies on a bridge layer to map JavaScript API calls to native platform implementations. The build process utilizes platform-specific toolchains, such as Xcode for iOS and Gradle for Android, to compile these binaries based on the settings defined in ti.app and ti.app-config . When integrating custom native
Symptom When building a Titanium project with the CLI, the build process frequently picks the most recently installed SDK even though the project’s tiapp.xml specifies a different <sdk-version> . This leads to build failures on CI pipelines that expect a stable, pinned SDK. Constraints & Uncertainties The SDK Manager can install multiple SDKs, but
The HTTPClient cache in Appcelerator Titanium stores responses keyed by URL and ETag, but does not automatically invalidate on server-side changes unless the request includes Cache-Control headers. On Android 10+, the default max-stale value of 0 disables tolerance for expired entries, triggering immediate freshness checks, yet the interaction between this b
sqlite