Skip to content

Issues: SandeepDhull1990/Appacitive-Android-SDK

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

13 Open 3 Closed
13 Open 3 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

AppacitiveConnection,s API fetchConnections...does not have paging info in the response, so it returns null.. bug
#18 opened Mar 1, 2013 by SoniaMane
Add a callback for delete operation on AppacitiveObject enhancement
#16 opened Feb 20, 2013 by SandeepDhull1990
@SandeepDhull1990
Not to make network call when saving an object having schema name value 'null'. bug
#15 opened Feb 20, 2013 by SandeepDhull1990
@SandeepDhull1990
For the null or empty api key the failure callback is not getting called. bug
#14 opened Feb 20, 2013 by SandeepDhull1990
Fix the entire AppacitiveFile api. Please refer to the iOS API for further clearance
#13 opened Feb 19, 2013 by aliHafizji
All getter should be thread safe bug
#11 opened Feb 19, 2013 by aliHafizji
Convert the Error code to a string and not use the + "" hack
#10 opened Feb 19, 2013 by aliHafizji
The developer should be able to initialise the Appacitive object using the global constructor.
#9 opened Feb 19, 2013 by aliHafizji
Application Context should be cached not the activity. This should be held in the Appacitive shared instance
#8 opened Feb 19, 2013 by aliHafizji
The developer does not need to pass a query with the "query=" string at the start.
#6 opened Feb 19, 2013 by aliHafizji
All responses cause enormous amount of GC. Needs to be fixed immediately.
#5 opened Feb 19, 2013 by aliHafizji
All callback should be on the UI Thread.
#4 opened Feb 19, 2013 by aliHafizji
Appacitive object is not thread safe and is leaking memory.
#3 opened Feb 19, 2013 by aliHafizji
@SandeepDhull1990
ProTip! Add no:assignee to see everything that’s not assigned.