briar issueshttps://code.briarproject.org/briar/briar/-/issues2017-07-17T15:02:45Zhttps://code.briarproject.org/briar/briar/-/issues/106Release beta versions through Google Play2017-07-17T15:02:45ZakwizgranRelease beta versions through Google PlayAndroid Beta 1akwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/982Crash when creating parent stack on Android 4.0.42017-08-01T16:58:38ZakwizgranCrash when creating parent stack on Android 4.0.4The Sony Xperia Tipo (Android 4.0.4) crashed with the following stacktrace when a blog invitation was received:
```
07-14 10:41:01.999 3782-3782/org.briarproject.briar.beta E/ACRA: ACRA caught a IllegalArgumentException for org.briarpro...The Sony Xperia Tipo (Android 4.0.4) crashed with the following stacktrace when a blog invitation was received:
```
07-14 10:41:01.999 3782-3782/org.briarproject.briar.beta E/ACRA: ACRA caught a IllegalArgumentException for org.briarproject.briar.beta
java.lang.IllegalArgumentException: android.content.pm.PackageManager$NameNotFoundException: ComponentInfo{org.briarproject.briar.beta/org.briarproject.briar.beta.android.navdrawer.NavDrawerActivity}
at android.support.v4.app.TaskStackBuilder.addParentStack(TaskStackBuilder.java:247)
at android.support.v4.app.TaskStackBuilder.addParentStack(TaskStackBuilder.java:226)
at org.briarproject.briar.android.AndroidNotificationManagerImpl.updateContactNotification(AndroidNotificationManagerImpl.java:315)
at org.briarproject.briar.android.AndroidNotificationManagerImpl.access$1200(AndroidNotificationManagerImpl.java:78)
at org.briarproject.briar.android.AndroidNotificationManagerImpl$3.run(AndroidNotificationManagerImpl.java:268)
at android.os.Handler.handleCallback(Handler.java:605)
at android.os.Handler.dispatchMessage(Handler.java:92)
at android.os.Looper.loop(Looper.java:137)
at android.app.ActivityThread.main(ActivityThread.java:4424)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:511)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:817)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:584)
at dalvik.system.NativeStart.main(Native Method)
Caused by: android.content.pm.PackageManager$NameNotFoundException: ComponentInfo{org.briarproject.briar.beta/org.briarproject.briar.beta.android.navdrawer.NavDrawerActivity}
at android.app.ApplicationPackageManager.getActivityInfo(ApplicationPackageManager.java:223)
at android.support.v4.app.NavUtils.getParentActivityName(NavUtils.java:301)
at android.support.v4.app.NavUtils.getParentActivityIntent(NavUtils.java:262)
at android.support.v4.app.TaskStackBuilder.addParentStack(TaskStackBuilder.java:240)
at android.support.v4.app.TaskStackBuilder.addParentStack(TaskStackBuilder.java:226)
at org.briarproject.briar.android.AndroidNotificationManagerImpl.updateContactNotification(AndroidNotificationManagerImpl.java:315)
at org.briarproject.briar.android.AndroidNotificationManagerImpl.access$1200(AndroidNotificationManagerImpl.java:78)
at org.briarproject.briar.android.AndroidNotificationManagerImpl$3.run(AndroidNotificationManagerImpl.java:268)
at android.os.Handler.handleCallback(Handler.java:605)
at android.os.Handler.dispatchMessage(Handler.java:92)
at android.os.Looper.loop(Looper.java:137)
at android.app.ActivityThread.main(ActivityThread.java:4424)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:511)
```
It makes sense to get a `NameNotFoundException` for `org.briarproject.briar.beta.android.navdrawer.NavDrawerActivity` because the package name is wrong - it should be `org.briarproject.briar.android.navdrawer.NavDrawerActivity` (without the `beta`). So it looks like this crash could be related to setting the package name in `build.gradle`.Android Beta 1akwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/979Removing contact fails after sharing blog2017-07-21T10:27:48ZakwizgranRemoving contact fails after sharing blogAfter sharing an RSS blog with a contact, both users get the following exception when trying to remove the contact:
```
07-07 17:46:07.045 7863-7923/org.briarproject.briar.beta W/ConversationActivity: org.briarproject.bramble.api.db.DbE...After sharing an RSS blog with a contact, both users get the following exception when trying to remove the contact:
```
07-07 17:46:07.045 7863-7923/org.briarproject.briar.beta W/ConversationActivity: org.briarproject.bramble.api.db.DbException
org.briarproject.bramble.api.db.DbException
at org.briarproject.briar.sharing.SharingManagerImpl.getSession(SharingManagerImpl.java:161)
at org.briarproject.briar.sharing.SharingManagerImpl.removingShareable(SharingManagerImpl.java:451)
at org.briarproject.briar.sharing.BlogSharingManagerImpl.removingBlog(BlogSharingManagerImpl.java:70)
at org.briarproject.briar.blog.BlogManagerImpl.removeBlog(BlogManagerImpl.java:224)
at org.briarproject.briar.blog.BlogManagerImpl.removingContact(BlogManagerImpl.java:119)
at org.briarproject.bramble.contact.ContactManagerImpl.removeContact(ContactManagerImpl.java:175)
at org.briarproject.bramble.contact.ContactManagerImpl.removeContact(ContactManagerImpl.java:137)
at org.briarproject.briar.android.contact.ConversationActivity$19.run(ConversationActivity.java:810)
at org.briarproject.briar.android.controller.DbControllerImpl$1.run(DbControllerImpl.java:37)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
at java.lang.Thread.run(Thread.java:818)
```
This is on the 977-crash-when-opening-rss-blog branch with freshly created accounts.Android Beta 1Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/977Crash when opening a blog2017-07-07T17:43:18ZakwizgranCrash when opening a blogAn anonymous user reported the following crash with Briar 0.13-alpha8 (an old build, so it may be fixed already):
```
java.lang.IllegalArgumentException
at org.briarproject.briar.sharing.SharingManagerImpl.respondToInvitation(Sh...An anonymous user reported the following crash with Briar 0.13-alpha8 (an old build, so it may be fixed already):
```
java.lang.IllegalArgumentException
at org.briarproject.briar.sharing.SharingManagerImpl.respondToInvitation(SharingManagerImpl.java:271)
at org.briarproject.briar.android.contact.ConversationActivity.respondToBlogRequest(ConversationActivity.java:1030)
at org.briarproject.briar.android.contact.ConversationActivity.access$3100(ConversationActivity.java:118)
at org.briarproject.briar.android.contact.ConversationActivity$26.run(ConversationActivity.java:969)
at org.briarproject.briar.android.controller.DbControllerImpl$1.run(DbControllerImpl.java:37)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607)
at java.lang.Thread.run(Thread.java:761)
```
"Crashed opening a Briar blog (RSS repost) shared via chat."
Android 7.1.2, Briar commit ID 7929ba9.Android Beta 1akwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/968H2 crashes on Android 4.0.42017-07-03T14:20:22ZakwizgranH2 crashes on Android 4.0.4Briar fails to start on the Sony Xperia Tipo (Android 4.0.4) because H2 crashes with the following stacktrace:
```
06-30 09:51:48.069 2888-3099/org.briarproject.briar E/ACRA: ACRA caught a NoClassDefFoundError for org.briarproject.briar
...Briar fails to start on the Sony Xperia Tipo (Android 4.0.4) because H2 crashes with the following stacktrace:
```
06-30 09:51:48.069 2888-3099/org.briarproject.briar E/ACRA: ACRA caught a NoClassDefFoundError for org.briarproject.briar
java.lang.NoClassDefFoundError: java.util.concurrent.ThreadLocalRandom
at org.h2.util.MathUtils.randomBytes(MathUtils.java:290)
at org.h2.engine.User.setUserPasswordHash(User.java:71)
at org.h2.engine.Engine.openSession(Engine.java:72)
at org.h2.engine.Engine.openSession(Engine.java:176)
at org.h2.engine.Engine.createSessionAndValidate(Engine.java:154)
at org.h2.engine.Engine.createSession(Engine.java:137)
at org.h2.engine.Engine.createSession(Engine.java:27)
at org.h2.engine.SessionRemote.connectEmbeddedOrServer(SessionRemote.java:354)
at org.h2.jdbc.JdbcConnection.<init>(JdbcConnection.java:116)
at org.h2.jdbc.JdbcConnection.<init>(JdbcConnection.java:100)
at org.h2.Driver.connect(Driver.java:69)
at java.sql.DriverManager.getConnection(DriverManager.java:175)
at org.briarproject.bramble.db.H2Database.createConnection(H2Database.java:93)
at org.briarproject.bramble.db.JdbcDatabase.startTransaction(JdbcDatabase.java:364)
at org.briarproject.bramble.db.JdbcDatabase.open(JdbcDatabase.java:271)
at org.briarproject.bramble.db.H2Database.open(H2Database.java:46)
at org.briarproject.bramble.db.DatabaseComponentImpl.open(DatabaseComponentImpl.java:117)
at org.briarproject.bramble.lifecycle.LifecycleManagerImpl.startServices(LifecycleManagerImpl.java:122)
at org.briarproject.briar.android.BriarService$1.run(BriarService.java:98)
```
It looks like the recent H2 upgrade has introduce a dependency on a newer version of Java.Android Beta 1akwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/966Sharing contact's blog fails with DbException2017-07-07T14:23:49ZakwizgranSharing contact's blog fails with DbExceptionLooks like this may have the same cause as #962.
```
06-01 02:02:06.140 25336-25418/org.briarproject.briar W/tSelectorControllerImpl: org.briarproject.bramble.api.db.DbException
org.briarproject.bramble.api.db.DbException
at...Looks like this may have the same cause as #962.
```
06-01 02:02:06.140 25336-25418/org.briarproject.briar W/tSelectorControllerImpl: org.briarproject.bramble.api.db.DbException
org.briarproject.bramble.api.db.DbException
at org.briarproject.briar.sharing.SharingManagerImpl.getSession(SharingManagerImpl.java:162)
at org.briarproject.briar.sharing.SharingManagerImpl.canBeShared(SharingManagerImpl.java:433)
at org.briarproject.briar.sharing.SharingManagerImpl.canBeShared(SharingManagerImpl.java:420)
at org.briarproject.briar.android.sharing.ShareBlogControllerImpl.isDisabled(ShareBlogControllerImpl.java:54)
at org.briarproject.briar.android.contactselection.ContactSelectorControllerImpl$1.run(ContactSelectorControllerImpl.java:54)
at org.briarproject.briar.android.controller.DbControllerImpl$1.run(DbControllerImpl.java:37)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
at java.lang.Thread.run(Thread.java:818)
```Android Beta 1Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/962Removing contact fails with DbException2017-07-04T15:19:30ZakwizgranRemoving contact fails with DbExceptionWith a fresh install of Briar, I added and removed a contact. Removing the contact succeeded on one device, but failed repeatedly on the other device with the following exception:
```
05-31 18:13:01.426 2390-2584/org.briarproject.briar ...With a fresh install of Briar, I added and removed a contact. Removing the contact succeeded on one device, but failed repeatedly on the other device with the following exception:
```
05-31 18:13:01.426 2390-2584/org.briarproject.briar W/ConversationActivity: org.briarproject.bramble.api.db.DbException
org.briarproject.bramble.api.db.DbException
at org.briarproject.briar.sharing.SharingManagerImpl.getSession(SharingManagerImpl.java:162)
at org.briarproject.briar.sharing.SharingManagerImpl.removingShareable(SharingManagerImpl.java:453)
at org.briarproject.briar.sharing.BlogSharingManagerImpl.removingBlog(BlogSharingManagerImpl.java:70)
at org.briarproject.briar.blog.BlogManagerImpl.removeBlog(BlogManagerImpl.java:224)
at org.briarproject.briar.blog.BlogManagerImpl.removingContact(BlogManagerImpl.java:119)
at org.briarproject.bramble.contact.ContactManagerImpl.removeContact(ContactManagerImpl.java:175)
at org.briarproject.bramble.contact.ContactManagerImpl.removeContact(ContactManagerImpl.java:137)
at org.briarproject.briar.android.contact.ConversationActivity$19.run(ConversationActivity.java:810)
at org.briarproject.briar.android.controller.DbControllerImpl$1.run(DbControllerImpl.java:37)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
at java.lang.Thread.run(Thread.java:818)
```
From the stacktrace, it looks like more than one session has somehow been created for sharing the contact's blog. (I didn't share the blog manually.)Android Beta 1Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/957Importing RSS feed case-sensitivity2017-07-04T15:10:19ZErnir ErlingssonImporting RSS feed case-sensitivityHad a test user who was unable to import an RSS feed, the button always stayed disabled. Turned out to be a case issue, we're only accepting lower-case but at the same time we're capping the first letter of the URL..Had a test user who was unable to import an RSS feed, the button always stayed disabled. Turned out to be a case issue, we're only accepting lower-case but at the same time we're capping the first letter of the URL..Android Beta 1akwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/956Tap protection UX problems2017-07-03T11:10:08ZErnir ErlingssonTap protection UX problemsThe current UX of the tap protection isn't good enough
***Test 1***
Three "regular" users: None of the users had a IT/CS background but all were familiar with Apps and their smartphones.
* All users were left insecure about the...The current UX of the tap protection isn't good enough
***Test 1***
Three "regular" users: None of the users had a IT/CS background but all were familiar with Apps and their smartphones.
* All users were left insecure about their devices security after reading the pop-up (all users got pop-ups, I've actually not seen a device yet that doesn't have at least one app which appears on the list.). Some wondered if they should even use Briar at all due to a security breach of their device.
* One user didn't recognise all the apps listed despite all of the being safe (I checked). This made the user very insecure about his phone's general security, got questions like "Did someone install something on my phone without my knowledge ?", "Do I need to virus scan my phone?", "Does this mean I shouldn't use Briar ?"
* Two testers weren't aware that it was even possible for other apps to steal taps and had to be educated in what this means exactly.
***Test 2***
Three software developers
* All three were a bit confused about the meaning (all three read it in German). All three understood roughly what it was about in the end but it was not smooth and the final understanding varied quite a bit.
* One user thought Briar was warning against screen-shot copying (the german text actually doesn't say "tap" anywhere, only "overlaying apps".
* One user felt that Briar had scanned his phone without permission to display the list of overlaying apps.
* All three wondered if the security risk really warranted such a dominating UI response from Briar and one suggested a warning triangle you could press for more information.
***End result***
We need re-design this on the UX level, we also need to bear in mind the variation in how security conscious the users are. I feel we should split this into basic information, which is always displayed, and advanced information when user requests it. I also felt the warning triangle idea was a good one.Android Beta 1akwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/954NPE: showNewScreenFilterWarning2017-06-30T12:21:59ZTorsten GroteNPE: showNewScreenFilterWarningI got this strange crash in the log:
```
05-19 12:04:13.178 I/ActivityManager: START u0 {flg=0x14000000 cmp=org.briarproject.unofficial/org.briarproject.briar.android.navdrawer.NavDrawerActivity (has extras)} from uid 10104 on display ...I got this strange crash in the log:
```
05-19 12:04:13.178 I/ActivityManager: START u0 {flg=0x14000000 cmp=org.briarproject.unofficial/org.briarproject.briar.android.navdrawer.NavDrawerActivity (has extras)} from uid 10104 on display 0
05-19 12:04:13.210 I/art: System.exit called, status: 0
05-19 12:04:13.210 I/AndroidRuntime: VM exiting with result code 0, cleanup skipped.
05-19 12:04:13.333 W/InputDispatcher: channel '9fb7829 org.briarproject.unofficial/org.briarproject.briar.android.navdrawer.NavDrawerActivity (server)' ~ Consumer closed input channel or an error occurred. events=0x9
05-19 12:04:13.333 E/InputDispatcher: channel '9fb7829 org.briarproject.unofficial/org.briarproject.briar.android.navdrawer.NavDrawerActivity (server)' ~ Channel is unrecoverably broken and will be disposed!
05-19 12:04:13.334 D/GraphicsStats: Buffer count: 23
05-19 12:04:13.334 I/WindowManager: WIN DEATH: Window{9fb7829 u0 org.briarproject.unofficial/org.briarproject.briar.android.navdrawer.NavDrawerActivity}
05-19 12:04:13.335 I/ActivityManager: Process org.briarproject.unofficial (pid 22636) has died
05-19 12:04:13.335 D/ActivityManager: cleanUpApplicationRecord -- 22636
```Android Beta 1Julian DehmJulian Dehmhttps://code.briarproject.org/briar/briar/-/issues/951Remove visibility indicators from private group join messages2017-07-04T15:10:19ZakwizgranRemove visibility indicators from private group join messagesThis is an experiment to see if we can reduce the confusion about revealing contacts by not exposing this feature until the user navigates to the reveal contacts screen, where we can show onboarding.
Related to #801, #854.This is an experiment to see if we can reduce the confusion about revealing contacts by not exposing this feature until the user navigates to the reveal contacts screen, where we can show onboarding.
Related to #801, #854.Android Beta 1akwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/948ArrayIndexOutOfBoundsException in VectorDrawable on Startup2017-06-09T19:25:50ZTorsten GroteArrayIndexOutOfBoundsException in VectorDrawable on StartupRight after Briar starts, it crashes on an GT-I9515L running Android 5.0.1 with this trace:
![804206593_51066](/uploads/c03850ad83619206fc77e4ca68cdb772/804206593_51066.jpg)Right after Briar starts, it crashes on an GT-I9515L running Android 5.0.1 with this trace:
![804206593_51066](/uploads/c03850ad83619206fc77e4ca68cdb772/804206593_51066.jpg)Android Beta 1Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/946Fab up/down button quick goto's for unread messages in threaded lists is not ...2017-06-09T19:25:50ZErnir ErlingssonFab up/down button quick goto's for unread messages in threaded lists is not always workingIf you enter a threaded list with unread messages the fab buttons aren't appearing when they should most of the time.If you enter a threaded list with unread messages the fab buttons aren't appearing when they should most of the time.Android Beta 1https://code.briarproject.org/briar/briar/-/issues/941Reblogged RSS post has wrong icon2017-06-09T19:25:50ZakwizgranReblogged RSS post has wrong iconWhen reblogging a post from an RSS feed, the reblogged post has the correct (RSS) icon for the original author when viewed on the device where it was imported:
![device-2017-04-13-145813](/uploads/85b44d910b5c997c7b44642be75c7a16/device...When reblogging a post from an RSS feed, the reblogged post has the correct (RSS) icon for the original author when viewed on the device where it was imported:
![device-2017-04-13-145813](/uploads/85b44d910b5c997c7b44642be75c7a16/device-2017-04-13-145813.png)
But when the reblogged post is viewed on a contact's device, is has an identicon and a trust indicator for the original author, instead of the RSS icon:
![device-2017-04-13-145903](/uploads/80e80b8ff9c9e6cdc8f326dc2ced3e94/device-2017-04-13-145903.png)
If the contact reblogs the post again, the twice-reblogged post has an identicon and a trust indicator for the original author on both devices:
![device-2017-04-13-145950](/uploads/902826ad1a284bbd869f17cbf9d269ca/device-2017-04-13-145950.png)
I guess there's a bug in the code that finds the root post and checks whether it comes from an RSS feed.Android Beta 1akwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/933Show beta warning screen during setup2017-12-18T07:40:20ZakwizgranShow beta warning screen during setupThe beta will be time-limited and forward-incompatible with later releases, so testers will lose their contacts and messages when the build expires. Show a warning about this during setup.
Perhaps we should repeat the warning a week bef...The beta will be time-limited and forward-incompatible with later releases, so testers will lose their contacts and messages when the build expires. Show a warning about this during setup.
Perhaps we should repeat the warning a week before the build expires.Android Beta 1Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/904Briar doesn't shut down if Tor has crashed2017-07-31T13:10:54ZakwizgranBriar doesn't shut down if Tor has crashedIf the Tor process crashes, Briar waits forever for the control port shutdown command to complete. It should eventually time out so that Briar doesn't need to be force stopped.If the Tor process crashes, Briar waits forever for the control port shutdown command to complete. It should eventually time out so that Briar doesn't need to be force stopped.Android Beta 1Julian DehmJulian Dehmhttps://code.briarproject.org/briar/briar/-/issues/894Remember list position and restore it2017-12-18T07:40:22ZTorsten GroteRemember list position and restore itOne of the testers moved a conversation from a forum discussion (that was supposed to be for more people) to a private conversation, because "forums are hard to read". When asked for more details and he said that you have to scroll down ...One of the testers moved a conversation from a forum discussion (that was supposed to be for more people) to a private conversation, because "forums are hard to read". When asked for more details and he said that you have to scroll down every time to the last message, so you have to real all the thread again and again like in a non-quoted email thread.
He said that it would help immensely, if Briar would remember the last message you had read and show it again when you re-enter the forum.
So this ticket is about remembering the list position and then restoring it when the screen is rotated or the user re-enters the list.
There are several list positions we could restore depending on which list is concerned:
* just the last known scrolling position before the list was left
* the position of the message that was marked as read last
* the position of the message that was marked as read first when the conversation was enteredAndroid Beta 1https://code.briarproject.org/briar/briar/-/issues/892Separate RSS posts from personal blog posts2017-12-18T07:40:22ZakwizgranSeparate RSS posts from personal blog postsThis is an umbrella ticket for discussing how to separate RSS posts from personal blog posts in order to solve some of the issues testers have reported with RSS feeds, such as #796 and #866.
Questions raise by @grote on #476:
> The cur...This is an umbrella ticket for discussing how to separate RSS posts from personal blog posts in order to solve some of the issues testers have reported with RSS feeds, such as #796 and #866.
Questions raise by @grote on #476:
> The current descriptor is a BdfList of `author_name (string), author_public_key (raw)`. Questions coming to mind are:
> * Do we tie RSS blogs to one author in the same way?
> * Will they use the same descriptor format, or can they use a different one depending on the flag?
> * Should we use an (int) as a flag to be able to add different blog types later or a (boolean)?
> * Do we add a title field to the descriptor?
> * Or should there maybe be a dedicated RSS client with a different client ID that inherits from the blog client?Android Beta 1Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/874Forums: Make tree indicator more visible2017-12-18T07:40:24ZMegaloxForums: Make tree indicator more visibleThe testers noticed that the tree indicator isn't visible enough.
I suggest we make the grey of the lines, the number and the outline of the circle at least 30% darker.The testers noticed that the tree indicator isn't visible enough.
I suggest we make the grey of the lines, the number and the outline of the circle at least 30% darker.Android Beta 1Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/867RSS feed: Posts from the RSS feed stayed in the blog after deleting the RSS feed2017-12-18T07:40:24ZMegaloxRSS feed: Posts from the RSS feed stayed in the blog after deleting the RSS feedThe testers had no problem deleting an RSS feed, but they expected the posts from the RSS feed to disappear.The testers had no problem deleting an RSS feed, but they expected the posts from the RSS feed to disappear.Android Beta 1Torsten GroteTorsten Grote